Mailman 3 June 2018 - Mailman-Users

Supressing storage of attachments
by Parker, Michael D. 27 Jun '18

27 Jun '18

On mailman2 .... I'd like to inhibit the storage of attachments in the archives. Is there a global option to inhibit this? Thanks.

2 6

Changing the name of existing mailing lists
by Parker, Michael D. 27 Jun '18

27 Jun '18

Is there a way to change the name of a mailing list? Thanks.

2 1

Re: [Mailman-Users] Changing the name of existing mailing lists -- found in wiki
by Parker, Michael D. 27 Jun '18

27 Jun '18

Found it in the Wiki....I am using the Method 3 (moving files)....what confused me was the fact that the name of the mailing list once changed contained the OLD name and not the NEW name. The Wiki entry addresses the fact too. Sorry. ***** ***** ***** ***** ***** ***** -----Original Message----- From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com(a)python.org> On Behalf Of Parker, Michael D. Sent: Wednesday, June 27, 2018 14:26 To: mailman-users(a)python.org Subject: -EXT-[Mailman-Users] Changing the name of existing mailing lists Is there a way to change the name of a mailing list? Thanks. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org https://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: https://mail.python.org/mailman/options/mailman-users/michael.d.parker%40ga…

1 0

can not add subscribers to list
by cwieland＠uci.edu 27 Jun '18

27 Jun '18

I have one list that will not add subscribers. I get this in the logs: subscribe:Jun 26 20:35:40 2018 (24695) cogsci-aic: pending "thehdguy(a)cathyscorner.us" <thehdguy(a)cathyscorner.us> 128.200.115.74 but it adds -owner to the address so the email fails Jun 26 20:35:41 department-lists postfix/smtp[24704]: 4A37512C057: to=<thehdguy-owner(a)cathyscorner.us>, relay=vade-in1.mail.dreamhost.com[66.33.205.212]:25, delay=0.49, delays=0.02/0.01/0.42/0.05, dsn=5.7.1, status=bounced (host vade-in1.mail.dreamhost.com[66.33.205.212] said: 550 5.7.1 <thehdguy-owner(a)cathyscorner.us>: Recipient address rejected: User unknown. (in reply to RCPT TO command)) I have looked thru the configuration and can not find anything unusual. Theis server has 100’s of lists. A quick check and other lists all seem to be working as expected. Any ideas would be greatly appreciated. Best, Con Wieland

2 2

How to track down someone mislabeling msgs as abuse?
by Richard Johnson 26 Jun '18

26 Jun '18

I have a mailing list which has 51 members, all friends of mine. We use it to communicate on things related to our history club. About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse". Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses. All I get is this: Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT) Source-IP: 98.173.52.230 Reported-Domain: mischievous.us Redacted-Address: redacted Redacted-Address: redacted@ Along with also a copy of the original message. Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that. (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!) I've read that some people have addressed this by inserting a unique string at the end of each person's message. I don't see a way to do this with Mailman 2.1.22. Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version? Are there other ways to address this? I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse! Any help would be greatly appreciated! /raj

4 7

Mailman 2.1.27 released
by Mark Sapiro 26 Jun '18

26 Jun '18

I am pleased to announce the release of Mailman 2.1.27. Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended. This is a routine bug fix release with a few new features and some minor security enhancements. See the attached README.txt for details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Mailman 2.1.27 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2

Global blacklist recipient address?
by Kevin Bowen 18 Jun '18

18 Jun '18

What is the best way to block a particular recipient address site-wide? I see there's a KNOWN_SPAMMERS variable, but I'm not sure if that's what I need since I want to block any mail from getting sent TO this address, not from it. Someone is being maliciously subscribed to multiple mailing lists and getting spammed with subscription requests. Kevin Bowen kevin.t.bowen(a)gmail.com <kevin(a)ucsd.edu>

2 3

Bouncing emails.
by Mark T 15 Jun '18

15 Jun '18

Hi is there any way I can stop my mailman list Members emails bouncing keeps saying to reply to the email they do that and it keeps happening Mark. Tune in to the number one station on the web TAFN radio http://tafn.org.uk/listen Or for our catch up service on demand http://www.tafn.org.uk/on-demand or for our upcoming weekly schedule http://www.tafn.org.uk/radio part of the accessible friends network www.tafn.org.uk Registered UK Charity: #1108043. Sent from Windows 10 Mail.

2 2

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

Mailman-Users June 2018