Mailman 3 June 2018 - Mailman-Users

Re: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
by Jeffrey Rolland 15 Jun '18

15 Jun '18

I tried using your script. The tar_list.sh script works fine. But, for the untar_list.sh script, I had two fairly big problems. 1) the mailman user account did not have a home director or shell; I fixed those problems handily. 2) I got a ton of permission/owner errors trying to untar the archives. The private archives on the new server appeared to have been owned by root, while the public archives appeared to be owned by www.-data; neither untar-ed well with the script being owned by mailman. Can you help? I'd really like to migrate my server today, and this is my last task before switching over the firewall exceptions to the new server's inside-NAT IP address. Thanks much in advance. Sincerely, -- Jeffrey Rolland <jrolland194(a)gmail.com> "The weed of crime bears bitter fruit; crime does NOT pay! The Shadow knows!" - The Shadow, _The Shadow_ (1994) -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GM d-- s:+ a+ C++>$ UL+>$ P? L+++>+++++$ E--- W+++>$ N+++>+++$ o? K--? !w--- !O---- !M- !V-- PS++ PE- Y? PGP+++ t+++ 5? X+ R+>$ tv++ !b DI+++>+++++ !D G+ e++++$ h+ r-- y++ ------END GEEK CODE BLOCK------ FWIW, I've done two complete migrations of a number of mailman (v2) lists as I've changed servers over the past few years. A couple of scripts I've used have worked perfectly in every case. In every migration, the basic Mailman installation is set up and running on the new server. Mailman versions, as long as we're talking about v2.x.x, are a no-nevermind. The first, which runs on the old server is called tar_list.sh, is kept in /usr/local/sbin and is run as root: #!/bin/sh if [ "$1" = "" ]; then echo 'Usage: tar_list.sh <listname>' exit fi if [ ! -e /var/lib/mailman/lists/$1 ]; then echo "$1: No such list!" exit fi mkdir /tmp/$1 cd /var/lib/mailman/lists/ echo Creating $1_list.tar.gz .... tar -czvf $1_list.tar.gz $1 mv $1_list.tar.gz /tmp/$1 cd /var/lib/mailman/archives/private/ echo Creating $1_archive.tar.gz .... tar -czvf $1_archive.tar.gz $1 mv $1_archive.tar.gz /tmp/$1 echo Creating $1_archive_mbox.tar.gz .... tar -czvf $1_archive_mbox.tar.gz $1.mbox mv $1_archive_mbox.tar.gz /tmp/$1 if [ -L /var/lib/mailman/archives/public/$1 ]; then touch /tmp/$1/$1_archive_is_public fi The second script, on the new server, lives in ~mailman/bin and is run as the mailman user (which, on my server, has a real, usable shell): #!/bin/sh if [ "$2" = "" ]; then echo 'Usage: untar_list.sh <server> <listname>' exit fi cd ~/tmp/ echo "Give root password on remote system ..." scp root@$1:/tmp/$2/* . cd /var/lib/mailman/lists/ echo "" echo "Creating list $2 ..." tar -xzvpf ~/tmp/$2_list.tar.gz cd /var/lib/mailman/archives/private/ echo "" echo "Creating archive for $2 ..." tar --same-owner -xzvpf ~/tmp/$2_archive.tar.gz echo "Creating archive mbox for $1 ..." tar --same-owner -xzvpf ~/tmp/$2_archive_mbox.tar.gz if [ -e ~/tmp/$2_archive_is_public ]; then ln -s /var/lib/mailman/archives/private/$2 /var/lib/mailman/archives/public/$2 fi echo"" echo "If no errors, delete files in ~/tmp and delete /tmp/$2 directory on remote system" This does require (and this may be a show-stopper for some) that the mailman user on the new system be able to ssh to the old server as root. I'm sure there's an easy workaround for this, but since I've always has full root access to my servers and run connections between servers via encrypted VPNs, it's been simply a matter of modifying the sshd_config file to allow this

4 4

Suppressing Archive AND Digest Generation and collection
by Parker, Michael D. 14 Jun '18

14 Jun '18

I previously asked how to permanently and globally remove archives. Based on a previous note, I added to my mm_cfg.py: GLOBAL_PIPELINE.remove('ToArchive') I assumed that the Digest file would be suppressed as well but I guess that is something different. I note that a digest file is now created in /var/lib/mailman/lists/<listname> for each note received to be reflected further. How can the digest functionality be globally suppressed as well. Thanks.

2 1

change listinfo url?
by Russell Clemings 13 Jun '18

13 Jun '18

The bots are killing me. I've set all of our lists to 'advertise' = 'no', but the bots are still hitting the /mailman/listinfo/listname URLs. Is there a straightforward way of changing that URL without changing the list or host name? Maybe make it /mailman/listinfo1/listname? All I can see in the faq/archives concerns changing the host/list name. -- =============================================== Russell Clemings <russell(a)clemings.com> ===============================================

3 12

Unsubscribe emails - saved anywhere?
by Andy Cravens 12 Jun '18

12 Jun '18

Using mailman 2.1.26. When someone sends an unsubscribe email to a mailman server, does that email get saved anywhere after it is processed?

2 1

pending subscription to list "mailman"
by Jim Popovitch 11 Jun '18

11 Jun '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, For some unknown reason a legitimate human sent a subscribe request to mailman-subscribe(a)domain.tld and now I'm receiving pending subscriber notifications for the "mailman" list, which isn't a list with an available web interface. Is there a cmd line way to discard pending subscribers? Also, should the mailman/data/aliases.db even contain aliases for the mailman list? tia, - -Jim P. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsesNcACgkQJxVetMRa JwVVCw//bsx0xZaY/9ypdkkhf/+zNEGB0i4yauLogAsZyeGaWz/CS2oCrlei6Ghm 0f95MdCBAegtbkRizQP0iMmYOsUmyul0K/22Cp8UJiHegqeMvsA99yvMgREiuhck nMDg1A+7s2yYy7VaZw390OMMWnfB23zjfGUQqvuGhR21mK8HyygxEYtzXK4jj2Sf n1EiEc9+UxiVIK27ZhiCkSm0jY5OJ5GaQpCV9KJ7x1cEn33suIzUwksiXvWeHJNu YgQ5tUZcY9f1Vk/iF6h5dcR05N+Dj3afnwp0p8SHesOlep2zwyIeH2UD2EbvuFTv dOlDpjspnhhbMzm2m1A+bDZaNd2wlBoC7Hzdm7Zru9LjuZtEz90HQvgAcD3rNEUj AtH1U/CKrmC9quDQFZPGdhzqIo3svFyJgF9havCYdUq3Dyt+FP6nVIR/D+amRWZQ CMrtAiyMJUPMdtj3UnsuZ3dH8VJSpxIf2nx0ztOhLGhIJcSs4aVe0dJ8iFwOaB/C 3rwtpJ9FDWyr2K2AQ8js7eepHQpp6ccxqkdC/D1E5L7bmPAz+HaBrNBeGACpFUn/ +uy0HlA1r4UC80Jx76Tl1sf1IVmEiI3JdZCjnDkIbhWilfwZ0OHub8YV/MuMyTdI dlExCvR95DGJMCOMUdVTKQNI3jZPORC3zX04YAvcRVvcWUrwSXM= =ScFr -----END PGP SIGNATURE-----

2 2

Repeating Outgoing Messages
by Brian Carpenter 10 Jun '18

10 Jun '18

Dear Mailman Community, I have a strange issue that has been occurring for the last 2 weeks. One of our mailman servers continues to have 4-5 messages stuck in the qfiles/out folder. These messages are being removed and then readded to the folder. The same messages over and over and over. It is causing significant I/O usage. I have to stop the mailman server and then manually remove the messages. They are coming from one list via different members. I checked the list archives and there is only one copy of each message listed in the archive and they are not being resent to list members. It's just that these 4/5 messages are being removed and then rewritten to the qfiles/out folder over and over. Suggestions? Brian Carpenter Owner Providing Mailman Hosting and more for over 15 years. T: 336.755.0685 E: brian(a)emwd.com www.emwd.com <http://www.emwd.com> www.mailmanhost.com <http://www.mailmanhost.com> <https://www.facebook.com/pages/EMWDcom/192156034142506> <http://www.linkedin.com/in/brianemwd>

2 6

Some patterns for ban_list and script to automatically update it
by Martin Schulte 09 Jun '18

09 Jun '18

Hello Mailman-Users, to cope with the still ongoing subscription spam I've started to maintain a list of patterns and a script to automatically load them to a list (in case to can't/don't want to use GLOBAL_BAN_LIST). Feel free to access them via git clone https://github.com/noabospam/abospam.git Greetings, Martin

2 1

Cascading lists
by Rubén Fernández Asensio 08 Jun '18

08 Jun '18

Hello all, I'm a new list administrator and a bit lost among Mailman's many features. Could you please give some advice? I'm trying to implement an announcement list and an unmoderated discussion list, and having the second receive all mail sent to the first one. The announcement list will prevent everybody but a few addresses to post, and will attach a personalized footer to every post with a link to the subscriber's option page. The discussion list will attach its own generalized footer. In sum, I want a single place to manage permissions to send announcements to both lists. I don't care about duplicates, as I want people to actively unsubscribe from the announcement list if they've joined both by mistake. However, it would be nice if the announcements received by the discussion list wouldn't have any personalized footer. Also, I want subscribers of the discussion list to be able to send replies to the announcement into the discussion list itself, whereas subscribers of the announcement list will get their own 'Reply-to' heading. What's the best setup to achieve this? Umbrella lists, sibling lists, or something else? Thanks in advance, Rubén Fernández

2 6

mailman-2.1.26: `make install` fails
by Brent Kearney 06 Jun '18

06 Jun '18

Hello, When I run 'make install’ on mailman-2.1.26 (with python 2.7), I get a fatal error in the “misc” directory. The complete output is below. I notice that the "for p in ; \” has an empty list of packages. Perhaps that for loop should be surrounded by a conditional checking that the $(PACKAGES) variable is non-empty? Best regards, Brent mailman-2.1.26]$ sudo make install Creating architecture independent directories... chmod o-r /opt/mailman/archives/private Creating architecture dependent directories... for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py export.py mailman-config; \ do \ /opt/csw/bin/ginstall -c -m 755 ../build/bin/$f /opt/mailman/bin; \ done for f in crontab.in; \ do \ /opt/csw/bin/ginstall -c -m 644 $f /opt/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled cull_bad_shunt; \ do \ /opt/csw/bin/ginstall -c -m 755 ../build/cron/$f /opt/mailman/cron; \ done for i in ./*.jpg ./*.png ./*.ico; \ do \ /opt/csw/bin/ginstall -c -m 644 $i /opt/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/opt/mailman/$d; \ /opt/csw/bin/ginstall -c -m 644 paths.py $dir; \ done /opt/csw/bin/ginstall -c -m 755 mailman /opt/mailman/scripts /opt/csw/bin/ginstall -c -m 644 sitelist.cfg /opt/mailman/data if [ -z "" -a -d /opt/mailman/pythonlib/email ] ; \ then \ rm -rf /opt/mailman/pythonlib/email* ; \ fi for p in ; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/opt/mailman/pythonlib /opt/csw/bin/python2.7 setup.py --quiet install --install-lib /opt/mailman/pythonlib --install-purelib /opt/mailman/pythonlib --install-data /opt/mailman/pythonlib); \ done sh: syntax error at line 1: `;' unexpected *** Error code 2 make: Fatal error: Command failed for target `install-packages' Current working directory /opt/src/mailman-2.1.26/misc *** Error code 1 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall'

2 4

Upgradeability of 2.1.* releases?
by Matěj Cepl 06 Jun '18

06 Jun '18

Hello, Where could I find how smooth is the upgrade between different 2.1.* releases? Are there any tools for the conversion of the configuration, if it is not completely automagical? I work for SUSE and we have 2.1.14 on SLE 11, but for https://bugs.launchpad.net/mailman/+bug/775294 it seems the only redress is upgrade to the latest release, right? Meanwhile, because of CVE-2016-6893 we will probably upgrade to 2.1.15, but from that to 2.1.26 is still a long way to go. Any advice? Thank you, Matěj Cepl -- https://matej.ceplovi.cz/blog/, Jabber: mcepl(a)ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Thou shalt not nede to be afrayed for any bugges by night. -- Coverdale's 1535 translation of Psalm 91 (or Christopher Higley's 1972 thesis explaining why programmers' are nocturnal beasts)

3 2