Mailman 3 December 2019 - Mailman-Developers

before next release: disable backscatter in default installation
by Jo Rhett Nov. 8, 2022

Nov. 8, 2022

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

Mail not being delivered
by ritwik p Jan. 3, 2020

Jan. 3, 2020

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

Introduction
by ritwikpuri5678＠gmail.com Dec. 21, 2019

Dec. 21, 2019

Hi everyone, My name is Ritwik and I would like to contribute to mailman project. I have worked with python on many personal projects and have a little bit of idea about Django. What would I like to work on?....I don't have a clue but would like to get better insight as I progress further. I'm using Ubuntu 18.04 LTS and am currently setting up the suite. Thank You

4 8

Recap: GSOD 2019
by ariessa.norramli＠gmail.com Dec. 12, 2019

Dec. 12, 2019

Hello everyone! Google Season of Docs has ended and the results for standard-length projects has finally been announced. I have successfully completed a project called 'Instructions for Migrating from Mailman 2 to Mailman 3'. My mentors were Stephen J. Turnbull and Abhilash Raj. I managed to create the following documentation: - What You Should Know Before Migration - How to Migrate from Mailman 2 to Mailman 3 - How to Start Contributing in Documentation - Documentation Template - Quickstart reStructuredText I would like to thank both of my mentors especially Stephen for guiding and giving me detailed comments and feedback throughout the whole GSOD phase. The comments and feedback were very helpful to me in producing the documentation. So once again, thank you very much for the great experience. I would love to continue contributing to the Mailman documentation. Anyway, my final project report can be viewed here: https://medium.com/@ariessa_norramli/summary-of-my-google-season-of-docs-jo… Thank you. Best Regards, Ariessa Norramli

1 0

Weekend releases
by Abhilash Raj Dec. 9, 2019

Dec. 9, 2019

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.1 - Django-mailman3 1.3.1 - Hyperkitty 1.3.1 These are all bugfix releases and include several fixes each. The full changelogs are available at: - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) Most notable fixes include a fix for PostgeSQL support in Hyperkitty, ability to delete a MailingList in Hyperkitty and list settings changes are immediately reflected in Hyperkitty (like making a List private). It also includes support for Python 3.8 and Django 3.0 in Postorius and Django-maialman3. Hyperkitty doesn't yet support either of them due to some dependencies not yet supporting Django 3.0 and a bug in Python 3.8.0 causing a test case failure[1]. I hope that we are able to support the latest and greatest as soon as possible, I am excited to be able to play with Django's aync capabilities. Finally, since our i18n workflow has been setup, we have lots of new translations coming in. This release also includes more parts of Postorius being translatable, including section headers. I am really happy to see Mailman 3 move closer to Mailman 2 in terms of i18n. If you want to help us improve the coverage, head on to Weblate[2]. All the releases are available on PyPI, as usual! [1] Fun Fact: The bug was due to a code that I contributed ;-). It is now fixed and will be soon out with Python 3.8.1 sometime this month. [2] https://hosted.weblate.org/projects/gnu-mailman/ -- thanks, Abhilash Raj (maxking)

1 0