Mailman 3 - Mailman-Developers

Rough Schedule for GSoC 2021 Community Bonding
by Steven Chen 18 May '21

18 May '21

Hello everyone, I am Quanwen Chen (the student being selected for this year's GSoC). You can call me Steven, and I use `Steven1677` as my username on GitLab. I am really glad to be selected, and my project is the list configuration tool. This tool is aimed at exporting/importing configurations of one list, so to start the project, I will try to figure out the database schema of mail lists first. Then some quick UI prototypes in postorius can be made for getting the basic feeling about the tool. As scheduled in my proposal, I will try to finish these two things in the community bonding period. However, I am taking exams in my university until May 28th. Hence, the work progress in the first two weeks of the community bonding period might be slow. But starting from May 29th, I am able to devote more time on this project. The focus of my working during the bonding period would be 1. figuring out what the tool should be in some kind of detail (make sure I will build the right thing, can use quick UI prototypes to validate) 2. getting more familiar with the database schema to support the coding period work I would like to thank two mentors: Stephen and Abhilash in advance for mentoring my work this summer. Regards, Steven

1 0

Re: [MM3-users] Core, Hyperkitty and Postorius releases
by Abhilash Raj 14 May '21

14 May '21

On Thu, May 13, 2021, at 1:46 PM, Odhiambo Washington wrote: > > > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for each components: >> >> Mailman Core 3.3.3: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> Postorius 1.3.4 https://docs.mailman3.org/projects/postorius/en/latest/news.html >> Hyperkitty 1.3.4 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html >> >> Minimum supported Python version is 3.6. >> >> You can install them using: >> >> $ pip install --upgrade postorius hyperkitty mailman >> >> We have also recently been working on making the installation instructions[1] to be >> more detailed and added a new FAQ[2] section for administrators where I hope >> to capture common questions from mailman-users list. >> >> Feedback or Merge Requests to improve these docs are welcome. You can either >> send an email or open an issue on Gitlab (easier to track) here[3]. >> >> [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > Hi Abhilash, > > What's the reason behind the exclusion of MySQL & Apache instructions in the installation instructions? :-) Really no reason, the intent was to pick some options in that page and point to additional documentation for using other alternatives. I will be more than happy to accept patches to add the documentation about alternatives like MySQL and Apache and other variations in the tech stack. Just add a new page under install/ and add a "Note" in the above page to point to it. I had documented some time ago how to contribute to our documentation[1] and folks on this list would be happy to answer any questions regarding contribution too. [1]: https://docs.mailman3.org/en/latest/documentation.html -- thanks, Abhilash Raj (maxking)

1 0

[Mailman-cabal] Invitation to the CERT Vendor Meeting 2021 [General-7305] - mailman
by Stephen J. Turnbull 23 Apr '21

23 Apr '21

Hi, There was recently a mail on the (closed) Mailman security list from the CERT Coordination Center which had this strange CC field: CC: '@mail.python.org, C(a)mail.python.org, E(a)mail.python.org, R(a)mail.python.org, T(a)mail.python.org, o(a)mail.python.org, r(a)mail.python.org, d(a)mail.python.org, i(a)mail.python.org, n(a)mail.python.org, a(a)mail.python.org, t(a)mail.python.org, e(a)mail.python.org, c(a)mail.python.org, "", "."@mail.python.org, g(a)mail.python.org I guess those are "conformant" email addresses, but they seem unlikely to be mailboxes at python.org. I'm not sure if these addresses were added by the generating software at CERT, some MTA, or Mailman. Has anybody seen anything like this before? P.S. I hope I'm not spoiling this for any amateur sleuths who wanted to figure it out for themselves, but yes, except for the apostrophe and the empty address, those are the letters in "CERT Coordination Center <cert(a)cert.org>", in order, with dupes eliminated. P.P.S. It's about a conference, not a CVE. Hakuna matata! Steve

2 2

Long lines in mail composed by HyperKitty
by Stephen J. Turnbull 21 Apr '21

21 Apr '21

Hi, [I prefer discussion be directed to mailman-developers, so Reply-To is set. But if you're not subscribed to -developers, following up here is OK, and I'll eventually summarize to -developers. Just don't followup to both.] I just noticed that among the agents that send non-conformant long lines[1] is HyperKitty. Nowadays violating the 80 octet limit is common and MUAs mostly handle it, but the 1000 octet limit is enforced by many MTAs[2] I think that HyperKitty should format mail per RFC 3676 format=flowed https://tools.ietf.org/html/rfc3676#section-4. However, I don't use "modern" (aka crappy HTML-oriented) clients, so I don't know whether they handle format=flowed properly. Discussion greatly desired. Steve Footnotes: [1] RFC 5321: MTAs MAY impose a limit >= 1000 octets including CRLF. RFC 5322: MUST be <= 1000 octets including CRLF, SHOULD be <= 80 octets including CRLF. [2] In practice, most (?) MTAs just break the line at 998 octets and insert CRLF rather than reject the message. I assume they would break happily in the middle of a multi-byte character, i.e., any non-ASCII in a UTF-8 text.

2 2

X-Mailman-Original-DKIM-Signature
by Alessandro Vesely 15 Apr '21

15 Apr '21

Hi, I discovered this just today, after a list I'm subscribed to enabled it. I have a filter which tries to validate original signatures by removing footers and subject tags. Removing "X-Mailman-Original-" is going to be the next addition. I guess the purpose of this option is to spare a dkim=fail result in the recipient's header. However, for documentation purposes[*], I'd be comforted by some document, discussion, or even a crispy comment about the intended usefulness of masking existing signatures. Google found nothing. Any pointer? TIA Ale -- [*] I try and document that original signature validation here: https://tools.ietf.org/html/draft-vesely-dmarc-mlm-transform

3 2

Mailman server showing internal server error (500)
by Prashant Pandey 08 Apr '21

08 Apr '21

I was using the mailman's development environment for a long time to understand the working and codebase. But today without changing anything I got a mailman server error 500. Is there any problem with mailman core? What troubleshooting is needed to fix this issue?

2 1

[GSoC] Some Questions in List Configuration Tool
by Steven Chen 08 Apr '21

08 Apr '21

Dear Mailman Developers, I am currently working on the proposal of List Configuration Tool in GSoC idea list. As I thought in the details of several functions of the tool, I wonder what kind of configurations should be exported, and what should not. Q1. We can get nearly all the configurations for a list from the core's REST API (https://mailman.readthedocs.io/en/release-3.1/src/mailman/rest/docs/listcon…), but some of the data should not be exported, such as `created_at`, `last_post_at`, and etc. Hence, we may need a filter to extract out the meaningful configurations to export out. I wonder whether we have a more convenient way to get all meaningful configurations, and what kind of configuration fields are expected to be exported from the user's perspective? Q2. Besides all the configurations obtained from the listconf mentioned in Q1, we have more configurations for a list, such as member list. In the Idea Page (https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021), it says that the membership roster should not be included by default. Since we already have the `list_mass_subscribe` method for importing a lot of subscriptions at once, so should the list configuration tool include the functionality to handle membership automatically or just does not include the memberships in the exported configuration? For Q1, I do have some thinking for some important configuration fields that should not be exported: owner_address: should be filtered out, since only the list owner can import the configuration template, the owner_address should be set when the owner apply the configuration template to the list instead of import from the previous configuration. mail_host, fqdn_listname: should be filtered out, since lists are created under the domains, domains should be created before the lists are created. Hence, only the name before the domain should be included in the exported configuration, and the full fqdn_listname can be generated when creating the list. I do need more suggestions on what to choose in the configuration that can be exported. Any suggestion is welcome. Regards, Steven1677

2 1

Interest to contribute under Mailman for GSoC 2021
by Aditya Komaravolu 31 Mar '21

31 Mar '21

Respected Developers, I am Aditya Komaravolu (Gitlab profile: https://gitlab.com/Aditya-Komaravolu), a second year student pursuing Bachelor of Technology from Vidya Jyothi Institute of Technology, India. I have done a few small contributions to the organization and I am confident enough that I will be able to contribute in a better way by learning from the mentors/developers of the organisation. GSoC is a very good opportunity to learn, bind and code with the community. I am very much interested to participate in GSoC 2021 for Mailman as a student. I would love to work for the project "Improved UI for Subscription Management " given in ( https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021). I really want to know what I should be learning to contribute/move in the direction of this project. Any support from your end would be highly appreciated ! Thank you, Aditya.

1 0

Interest to participate in GSoC under mailman
by Shubhank Saxena 31 Mar '21

31 Mar '21

Respected Mailman Developers My name is Shubhank(https://gitlab.com/shubhank-saxena). I am a final year engineering undergraduate from India. I am interested to participate in GSoC 2021 under Mailman. I have gone through the instructions provided by the organisation, and have got one of my MR reviewed and merged in the Mailman Core. I have now started to write a proposal in the same direction and I was wondering how can I start the discussion regarding the Mailman Core projects that are given on the webpage ( https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202021). I am interested in the project "Support for REST Callbacks in Core". Also, is the IRC channel active? I did not see any conversations happening so I was wondering if the mode of communication has shifted strictly to the mailing list? Thank you for your time!

2 2

Question about GSoC SPAM
by Steven Chen 29 Mar '21

29 Mar '21

Dear Mailman Developers, This is Steven1677(https://gitlab.com/Steven1677) on GitLab. I want to contribute to the mailman3 project as a GSoC student. I am starting to write my proposal for GSoC. I wonder whether our personal information will go public if we send the proposal to the this mail list? I fully understand that applying for GSoC requires such information, but I think the personal contact information (like phone number, email addresses) should be only available to the members of the developer team instead of the whole internet. Hence, I am asking whether the whole proposal (including the basic information of the student) should be sent to this mail list? Regards, Steven1677

3 4