Mailman 3 January 2020 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett 07 Nov '22

07 Nov '22

Hi. There's a fairly simple problem here that needs to be addressed. And it's mostly a documentation/install problem. I'm hoping we can get this resolved before the next release. PROBLEM: Mailman comes out of the box ready to backscatter spam people. Yes, it's easy enough to fix. But because it comes stock this way, and is documented to install this way, most people install it to do this. Those of us who work in abuse departments are tired of hearing "well that's how Mailman works". We also object to having to teach people how to fix their mailman installations because it's not documented in the current manual. This is *exactly* like Sendmail 14 years ago. We didn't accept it then, and Sendmail fixed the problem. RESOLUTION: Mailman default installation should not backscatter in a default configuration. 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by default. Nearly everyone uses web based signup. 2. Discard or hold messages from non-subscribers by default. I would think that it would be perfectly reasonable to have documentation on how to enable the 1980s-style -request / -subscribe etc aliases. However this documentation should have a note that this is against the AUP of nearly every network provider, and enabling it will likely cause them to get listed in various blacklists as a backscatter source. FYI: I know that this goes against the instincts of many old-time mailing list advocates here. But after dealing with a 10k/hour backscatter DoS my tolerance for this problem is understandably limited. Yes, it was a sweet day back in the 1980s. I was running a mailing list server and several UUCP gateways at the time, so I remember them well. But those days are past, and we need to deal with the reality of today. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness

21 168

Mailman 2.1.30rc1 released
by Mark Sapiro 19 Feb '20

19 Feb '20

I am pleased to announce the release of Mailman 2.1.30rc1. 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. See the attached README.txt for details. Mailman 2.1.30 will be the last release of the Mailman 2.1 branch from the GNU Mailman project. It contains some new strings which are untranslated in most of the i18n translations. If you can help update any of the translations, please contribute your changes. Changes can be submitted via a bzr merge proposal on Launchpad or by sending an updated mailman.po file and or templates directly to me. This will be the last chance to get i18n updates into a release. 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/ Mailman 2.1.30rc1 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

1 2

Regarding issue #553 in mailman-core
by ritwik p 18 Feb '20

18 Feb '20

The mentioned issue: https://gitlab.com/mailman/mailman/issues/553 So, the line 65 in `eml_confirm.py` in `/src/mailman/commands/` which raises the error is `assert member is None, member` Basically what this line is doing is checking if the `member` is `None` or not and if it ISN'T, it raises an Assertion Error with member details printed. According to the comments (line 57-60) in the same file, member would be `None` when there's an unsubscription, but here it is NOT None (idk why). 2 pretty simple ways of dealing with this will be: - commenting the line - adding an `except AssertionError` line But these won't solve the root problem, i.e why is the member NOT None. I'm currently looking a bit more into it but, How should I proceed with this?? Also, couple of doubts: - How can a moderator confirm the unsubscription request?? - For the tables `user` and `member` in `mailman.db` file in `mailman/var/data/`, when a person unsubscribes from a list, the entry of that member is deleted from the `member` table but not from `user` table. Is it due to the fact that even if the person is not a member, they can still be user?? Thank You

2 13

where to configure max_days_to_hold on MM3 GUI interface?
by Shashikanth Komandoor 29 Jan '20

29 Jan '20

Hi Sir, I came to know that the held messages can be restricted to be processed after a specific no of days or can be discard after some days using the parameter *max_days_to_hold*. But I could see that parameter value configurable on MM2 GUI interface in General Options but I don't see the same on the MM3 GUI interface. Could you please help me if I am missing something? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 2

Cron of Mailman notify is not working
by Shashikanth Komandoor 28 Jan '20

28 Jan '20

Hello, With your help, I was able to setup mailman 3.3 on my RHEL 7.5 machine and running well and good. For daily notification I have added the below line in the crontab: 00 08 * * * /var/lib/mailman/venv3/bin/mailman notify But this cron job is not working while I was able to run the same command manually at my CLI. Please help if there is any issue with mailman 3.3 or cronjob. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 1

Can I install Mailman 3.3 on RHEL 8 ?
by Shashikanth Komandoor 25 Jan '20

25 Jan '20

Hi Team/Sir, Can Mailman 3.3 be installed on RHEL 8? I got this query because while I was trying to install the prerequisites for Mailman 3.3 as per the website http://docs.mailman3.org/en/latest/devsetup.html I found nodejs-less is also to be installed. But I don't find the nodejs-less as part of BaseOS packages or the AppStream modules. Please suggest how to go ahead. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 1

Daily Summary of pending requests are not being sent
by Shashikanth Komandoor 24 Jan '20

24 Jan '20

Hi Sir/Team, As per the URL < https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs>, I understood that the command "mailman notify" is responsible to send the daily notifications to the owners of the list which of course should be as part of the cron job list (but it is not in my case). FYI, I am using mailman 3.2.3. And in my case, when I run the command "mailman notify" I am getting an error saying that the command "notify" is not present. *(venv3) [root@mailman3 commands]# mailman notifyUsage: mailman [OPTIONS] COMMAND [ARGS]...Try "mailman -h" for help.Error: No such command "notify".* And I also saw the help menu of mailman where I don't find any command displaying "notify" and its explanation. Is it the problem with this version or had I done wrong? Could you please help me in this regard? If I need to add the cron jobs manually I will try to add but please suggest what could be added? -- Thanks & Regards, Shashi Kanth.K 9052671936

2 1

Another set of new releases
by Abhilash Raj 12 Jan '20

12 Jan '20

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

1 0

Mail not being delivered
by ritwik p 03 Jan '20

03 Jan '20

Hi, So I've been trying to send mail via the `inject` command from the core. But having trouble with that. Currently, my list's subscription/unsubscription policy is `confirm` which basically means the subscriber who sends an email should get a confirmation email when he/she sends the mail to unsubscribe/subscribe (right?) As my user is trying to unsubscribe from the list (notgood(a)abcd.com) This is what I'm executing: mailman inject -f - -q command notgood(a)abcd.com From: 1111(a)rise.xyz To: notgood-leave(a)abcd.com Subject: unsubs Message-ID: <2_19_am_30dec(a)rise.xyz> messsssss Currently my inject-ed mail is in deferred queue in postfix and unable to reach the destination due to which I'am not able to confirm to leave the list. My postfix's logs are: postfix/smtpd[12722]: connect from localhost[::1] postfix/smtpd[12722]: 479834565D: client=localhost[::1] postfix/cleanup[12726]: 479834565D: message-id=<157763017885.12683.12681065635725544097@Ratwik> postfix/qmgr[12526]: 479834565D: from=<notgood-bounces(a)abcd.com>, size=808, nrcpt=1 (queue active) postfix/smtpd[12722]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 postfix/qmgr[17475]: 479834565D: from=<notgood-bounces(a)abcd.com>, size=808, nrcpt=1 (queue active) postfix/error[21664]: 479834565D: to=<you(a)yourdomain.com>, relay=none, delay=15789, delays=15758/31/0/0.11, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to nullmx.domainmanager.com[45.63.18.247]:25: Connection timed out) I also ran : postcat -vq 479834565D which gave me this: postcat: name_mask: all postcat: inet_addr_local: configured 4 IPv4 addresses postcat: inet_addr_local: configured 2 IPv6 addresses *** ENVELOPE RECORDS deferred/4/479834565D *** message_size: 808 665 1 0 808 0 message_arrival_time: Mon Dec 30 02:19:26 2019 create_time: Mon Dec 30 02:19:26 2019 named_attribute: log_ident=479834565D named_attribute: rewrite_context=local sender: notgood-bounces(a)abcd.com named_attribute: log_client_name=localhost named_attribute: log_client_address=IPv6:::1 named_attribute: log_client_port=44800 named_attribute: log_message_origin=localhost[::1] named_attribute: log_helo_name=[192.168.0.111] named_attribute: log_protocol_name=ESMTP named_attribute: client_name=localhost named_attribute: reverse_client_name=localhost named_attribute: client_address=::1 named_attribute: client_port=44800 named_attribute: server_address=::1 named_attribute: server_port=25 named_attribute: helo_name=[192.168.0.111] named_attribute: protocol_name=ESMTP named_attribute: client_address_type=10 named_attribute: dsn_orig_rcpt=rfc822;you(a)yourdomain.com original_recipient: you(a)yourdomain.com recipient: you(a)yourdomain.com *** MESSAGE CONTENTS deferred/4/479834565D *** regular_text: Received: from [192.168.0.111] (localhost [IPv6:::1]) regular_text: by Ratwik.www.tendawifi.com (Postfix) with ESMTP id 479834565D regular_text: for <you(a)yourdomain.com>; Mon, 30 Dec 2019 02:19:26 +0530 (IST) regular_text: Subject: The results of your email commands regular_text: From: notgood-bounces(a)abcd.com regular_text: To: 1111(a)rise.xyz regular_text: MIME-Version: 1.0 regular_text: Content-Type: text/plain; charset="us-ascii" regular_text: Content-Transfer-Encoding: 7bit regular_text: Message-ID: <157765256493.25261.11498683579672973569@Ratwik> regular_text: Date: Mon, 30 Dec 2019 02:19:24 +0530 regular_text: Precedence: bulk regular_text: X-Mailman-Version: 3.3.1 regular_text: regular_text: The results of your email command are provided below. regular_text: regular_text: - Original message details: regular_text: From: 1111(a)rise.xyz regular_text: Subject: unsubs regular_text: Date: Mon, 30 Dec 2019 02:19:24 +0530 regular_text: Message-ID: <2_19_am_30dec(a)rise.xyz> regular_text: regular_text: - Results: regular_text: No such command: unsubs regular_text: No such command: ooooonooooo regular_text: regular_text: - Done. *** HEADER EXTRACTED deferred/4/479834565D *** *** MESSAGE FILE END deferred/4/479834565D *** My `smtp.log` file in `mailman/var/logs/` shows: smtp to notgood(a)abcd.com for 1 recips, completed in 0.19297552108764648 seconds post to notgood(a)abcd.com from notgood-bounces(a)abcd.com, 598 bytes Also I had updated `mailman.cfg` file in `/mailman/etc/` with this: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix Also, as various forums were pointing towards that port 25 might be blocked, I ran : telnet localhost 25 which gave me 220 status code (which means it's open right?) How can I fix this so that my mail gets to the `list-leave` and thus receive confirmation to do the same?? Thank You

3 9

Mailman-Developers January 2020