Mailman 3 May 2018 - Mailman-Users

[Mailman-cabal] GDPR
by Andrew Hodgson May 31, 2018

May 31, 2018

Guys, Thanks for all the discussion around this topic. I have been in further communication with the people working on GDPR with us. Background: I run Mailman lists for a couple of charities as a voluntary contribution to the charities, the charities have money that their disposal and we want to reduce exposure both for me personally and the charities involved. These are just rough notes: - Archive purge requests. We have discussed the same items as on the list to date. I am looking at doing a simple grep for the relevant person's details and changing that. The main reason for doing this is that if we just remove the author's messages they will be in a thread of other messages and our users typically don't remove quoted material. Current advice from the GDPR people is we may have to delete the whole thread. Still under discussion, this is also complex because threads and subjects change, if we delete the whole thread there may be messages from the same author in other threads that don't have correct atribution etc. - Audit logs for data access. it is not clear who is accessing subscription data for the list as there is just a single owner and moderator account. Unsure if current logging data in either MM2 or MM3 is "good enough" for this. MM3 may solve the issue about single accounts. - Relevant people seem to be happy that running a discussion list not used for marketing purposes should exempt us from some of the marketing type rules regarding data processing. - People seem happy with the system default logs as long as we can audit access to the logs (which we are able to as there is little access to the boxes themselves). - Likely that I will have to move the lists to a host the charities control themselves and a separate host for each charity. This will increase costs so we may need to look at an alternative solution like a hosted list service as I am not setting myself up as a list hosting business. Again all this up for interpretation. The largest ones for me at the moment is regarding auditing access to the Mailman admin access and the archive purging requests. Andrew.

9 20

Duplicate command results
by Rubén Fernández Asensio May 31, 2018

May 31, 2018

Hello all, It's a tiny issue but really nags me. When a user sends a command to the request address (so far I've tried 'help' and 'set help') the reply shows the command's results twice, repeated within the same message. How could I fix this?

3 2

Re: [Mailman-Users] confirmation string is not working
by Henrique Fagundes May 30, 2018

May 30, 2018

Dear, To give continuity to this topic that I found on the internet (https://mail.python.org/pipermail/mailman-users/2012-May/073367.html) I also went through that. I solved this problem by disabling https. So that when redirecting from http to https occurred, the cache was lost. Forgive me for any incorrect spelling. I am Brazilian and I have difficulties with English. Regards, Henrique Fagundes suporte(a)aprendendolinux.com Skype: magnata-br-rj Linux User: 475399 https://www.aprendendolinux.com https://www.facebook.com/AprendendoLinux https://youtube.com/AprendendoLinux https://twitter.com/AprendendoLinux https://telegram.me/AprendendoLinux ______________________________________________________________________ Participe do Grupo Aprendendo Linux https://listas.aprendendolinux.com/listinfo/aprendendolinux Ou envie um e-mail para: aprendendolinux-subscribe(a)listas.aprendendolinux.com

2 2

Unsubscribe link
by nikos May 30, 2018

May 30, 2018

Hello list. Is possible to insert somehow a unsubscribe link inside the message instead in footer? After many tries I manage to put a direct link in footer, setting Full Personalization ON first. The problem is that Outlook attach footer and most users ignore it. So it could be useful to putt a link inside message. I use version 2.1.12 on Centos 6. Thank you in advance

5 5

updating mailman
by Mark T May 30, 2018

May 30, 2018

Hi can anyone give me easy instructions to update mailman Using the apt-get install process Also will it keep all my mailing lists and members Many thanks 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 1

Filtering messages with no subject
by Bryan Blackwell May 29, 2018

May 29, 2018

Hi folks, I'm having trouble with some spam using spoofed addresses getting through to my lists, they all seem to have no subject. I don't see any obvious way to filter these, am I missing an option? If not, has anyone implemented a filter to block these sorts of messages? Thanks for any help, --Bryan -- Bryan Blackwell -- Unix Systems Engineer bryan(a)skiblack.com

2 3

(2.1.26) Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Cannot open wrapper configuration file: No such file or directory
by michaelof＠rocketmail.com May 29, 2018

May 29, 2018

Hello to all, first post to this mailing list, so first of all thank you very much to all who helped to make Mailman and it's community reality! I'm running mailman now for a while without issues. On my VPS, not a big installation, not many lists, just a few users per list. After upgrading the VPS to OpenSuse Leap 15.0, Mailman still 2.1.26, Apache from 2.4.23 to 2.4.33, Python from 2.7.13 to 2.7.14, I'm getting the error message in the subject of this mail when trying to access the mailman web pages on Apache. All other Apache sites (non-Mailman, like TYPO3, Nextcloud, Roundcubemail, ...) / their Vhosts are running fine. Relevant part of Apache's error_log: [Tue May 29 11:46:07.135217 2018] [cgi:error] [pid 24758] [client (IPV6)] AH02811: script not found or unable to stat: /usr/lib/mailman/cgi-bin/favicon.ico [Tue May 29 11:46:07.486058 2018] [cgi:error] [pid 24758] [client (IPV6)] AH02811: script not found or unable to stat: /usr/lib/mailman/cgi-bin/error [Tue May 29 11:46:07.267081 2018] [cgi:error] [pid 25456] [client (IPV6)] AH02811: script not found or unable to stat: /usr/lib/mailman/cgi-bin/favicon.ico [Tue May 29 11:46:07.486381 2018] [cgi:error] [pid 25456] [client (IPV6)] AH02811: script not found or unable to stat: /usr/lib/mailman/cgi-bin/error --> which is true, but "favicon.ico" and "error" also haven't been existing on the fine running Mailman instance before the OpenSuse upgrade, checked in server backups. - I've compared (diff) Apache's config files (before and after the upgrade) file by file, most of them, esp. all direct Mailman files, are untouched by the upgrade, others (general httpd) with smaller changes, which really shouldn't affect Mailman. - Got the hint from #httpd, that the error msg has nothing to to with apache itself. Tested to run e.g. "listinfo" manually, same error: vserver:/usr/lib/mailman/cgi-bin # ./listinfo Content-type: text/html <head> <title>Mailman CGI error!!!</title> </head><body> <h1>Mailman CGI error!!!</h1> The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: <pre> Cannot open wrapper configuration file: No such file or directory</pre> - In contrast the executables in /usr/lib/mailman/bin are working fine, tested with e.g. "version", "check_db", "list_lists", all working as expected - Also Mailman systemd unit seems to run fine: vserver:~ # systemctl status mailman ● mailman.service - LSB: Starts the mailinglist manager Mailman Loaded: loaded (/etc/init.d/mailman; generated; vendor preset: disabled) Active: active (running) since Mon 2018-05-28 19:39:09 CEST; 16h ago Docs: man:systemd-sysv-generator(8) Tasks: 9 (limit: 629145) CGroup: /system.slice/mailman.service ├─1946 /usr/bin/python /usr/lib/mailman/bin/mailmanctl --quiet --stale-lock-cleanup start ├─1948 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s ├─1949 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s ├─1950 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s ├─1951 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s ├─1952 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s ├─1953 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s ├─1954 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s └─1955 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s Mai 28 19:39:08 vserver systemd[1]: Starting LSB: Starts the mailinglist manager Mailman... Mai 28 19:39:09 vserver mailman[1933]: Starting mailman..done Mai 28 19:39:09 vserver systemd[1]: Started LSB: Starts the mailinglist manager Mailman. - Vhost definition, unchanged: <IfDefine SSL> <IfDefine !NOSSL> <VirtualHost *:443> ServerName mailman.domain.tld:443 Include /etc/apache2/conf.d/mailman.conf DirectoryIndex listinfo ScriptAlias / /usr/lib/mailman/cgi-bin/ # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on <IfModule mod_headers.c> Header always set Strict-Transport-Security "max-age=15552000; preload" </IfModule> </VirtualHost> </IfDefine> </IfDefine> Stopping now with config files, avoiding getting this mail bigger and bigger :-) As I'm completely running of of ideas now, I would be very happy about new ideas/hints what might be the problem, where to continue searching for the issue. Thanks in advance, regards, Michael

2 5

Invite subscribers via command line.
by Jacques May 25, 2018

May 25, 2018

Hello, Due to new rules and regulations I will have to massively INVITE subscribers. I have some idea on how to (shell)script Subscribe (add_members (-r|-d) file list) but I am afraid a -invite key does not exist (yet) to massively Invite subscribers. Any chance to get this feature ? Thanks, Jacques -- GnuPg : C8F5B1E3 WeUsePGP Because privacy matters http://weusepgp.info/

2 6

Subscription via email
by Gretchen R Beck May 25, 2018

May 25, 2018

Is it possible to subscribe members to a list via email (for the admin to send an email with one or more addresses to subscribe to a list -- similar to the mass subscription page)? Gretchen Beck Carnegie Mellon

2 1

Probable bug in Bouncers/DSN.py
by Jim Popovitch May 24, 2018

May 24, 2018

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! Given a bounce msg with a subpart of: message/delivery-status: Final-Recipient: rfc822;user(a)domain.tld Action: failed Status: 5.1.10 Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound; and the code beginning at Bouncers/DSN.py:64 params = [] foundp = False for header in ('original-recipient', 'final-recipient'): for k, v in msgblock.get_params([], header): if k.lower() == 'rfc822': foundp = True else: params.append(k) if foundp: # Note that params should already be unquoted. addrs.extend(params) break It appears that "params" is never populated and thus the bounce score is never incremented for the user. I was intending to release a patch for this but my dev system is showing an odd python issue where once "k.lower()" is evaluated the variable v is no longer available. O.o - -Jim -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsG3PUACgkQJxVetMRa JwVnzA/+NJnsWa2bTEo689I7KsoIubwUlf6KPv1jIGU+98gKecOGFOlc9YAx6dU4 TiWPqkLG6oKYZti7Y/kjVxhmxKvj0Pb6xos8uJBqRikDKJQDbZjo+hVY1yR6zAL7 r1NIVc7BKsvTTQ+U4D4k4Y2D1WdOEGIYWdV0ds3SScc2eq6CM2nulI/YM7U32pdi YB4FTxK51K+8OYK9tprJEtSDgTADPiYjOb/qUTM1Zxnsdx6NK+q6MCTzUFilrgl8 pWOoIrmdrMyytRMgNp40arK8LMbD406P9kmDpuSU9/kPkFE7T98uRuD1II24m7MZ W8QtSPbmQDBWqKbu3/KmnC8OGiIO05KW9PHwt9fNWmqA/nSRbQ7tKZOkywRZIfQt 6RwJGqZnvRR5qk6ltIRNm/Cq3AQgGHD2m40m9ppSrGaeijtfNWfQnTnDCYB3P6d1 hnAxnDJ8UCxK3v4gQUeOf9xsfCaT5hss+vp6C1nZPfM7jupQWQxA4SjGH77Q47Wd SkqZvOPZ0lVajBvFKoNlttdrvXjeDBRki1v5hFvuNSHSMBSJ+yySb0FMuC3aw+2y KKZhKhwYJuoWMHMa6Lmhrtna/x1ywD1xvCg2m0J2mEM3biNFlwIHx7zewYbhn56j wTtX9Ch8ozdKVGakmybxfo91xkbQvRpROpjwIslRWrbxAgbV6r8= =z4V/ -----END PGP SIGNATURE-----

1 1