- Mailman-users - lists.mailman3.org

Using the API to create nonmembers with a different moderation action than the list default
by Perry Kollmorgen 08 Jun '24

08 Jun '24

Hi, My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. When using the mailmanclient python bindings I have worked out I can add nonmembers with something like: mailing_list.add_role('nonmember', 'nonmember(a)yourdomain.com', display_name='Non Member') However I can't see anything in the mailmanclient docs which suggest it is possible to configure a member_moderation_action or moderation_action field for that member. I assume I'll need to fall back to using the REST API directly, and most likely something along these lines: 1/ Obtain the member ID for an email address of someone who already been added as a nonmember. 2/ Patch an endpoint which looks something like: /members/{member_id} I'm not able to use the mailman binary (e.g mailman shell) on the mailman-core host itself as I would like to query an existing database of people and reach out to a mailman endpoint from the database host rather than opening that host up to further network access. I figured it might be a good stage in which to ask for a little help and pointers before I continue, perhaps there is something I have missed for a better way to approach this. Thanks. Regards, Perry

3 4

Trying to save a new style
by Perry Kollmorgen 07 Jun '24

07 Jun '24

Dear Mailman-users list, I have embarked on project to stand up a Mailman3 instance for general staff email announcements and a small number of adhoc lists. I have a fair amount up and working using Docker and Postfix, with generally emails to/from lists working well, as well as the web interface. One of the reasons I've used Mailman3 is the API and mailman shell options which I'm slowly trying to wrap my head around, but having some progress. I have a question for the moment on something which has stumped me, and whilst I may have more questions as I continue on this implementation, I am hopeful someone can point out where I am going wrong on this. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> >>> >>> from zope.interface import implementer >>> from mailman.interfaces.styles import IStyle >>> @implementer(IStyle) ... class TestStyle: ... name = 'AB-Announce-Style' ... description = 'AB Announce mailing list style.' ... def apply(self, mailing_list): ... mailing_list.admin_immed_notify = true ... mailing_list.admin_notify_mchanges = true ... mailing_list.advertised = false ... mailing_list.allow_list_posts = false ... mailing_list.anonymous_list = false ... mailing_list.archive_policy = "private" ... mailing_list.archive_rendering_mode = "markdown" ... mailing_list.collapse_alternatives = false ... mailing_list.convert_html_to_plaintext = false ... mailing_list.default_member_action = "defer" ... mailing_list.default_nonmember_action = "hold" ... mailing_list.digest_send_periodic = false ... mailing_list.digests_enabled = false ... mailing_list.emergency = false ... mailing_list.include_rfc2369_headers = true ... mailing_list.max_message_size = 40000 ... mailing_list.max_num_recipients = 30 ... mailing_list.member_roster_visibility = "moderators" ... mailing_list.send_goodbye_message = true ... mailing_list.send_welcome_message = true ... mailing_list.subscription_policy = "moderate" ... mailing_list.unsubscription_policy = "moderate" ... >>> manager.register(TestStyle()) >>> >>> commit() >>> >>> for style in manager.styles: ... print(style.name) ... AB-Announce-Style legacy-announce legacy-default private-default So at this point the style has been registered, however it doesn't look to save this permanently. When I quit the shell and log back in, it only shows the original 3 styles. Nor can I see the style from the web interface. Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from zope.component import getUtility >>> from mailman.interfaces.styles import IStyleManager >>> manager = getUtility(IStyleManager) >>> >>> for style in manager.styles: ... print(style.name) ... legacy-announce legacy-default private-default >>> Is there a way to save this style permanently ? Thank you for any assistance you can provide. Regards, PerryK

3 2

Mailman3 memory footprint
by Marc SCHAEFER 06 Jun '24

06 Jun '24

Hello, It seems the mailman & mailman-web memory footprint are somewhat big. It looks a lot of instances are started. I have seen this: https://gitlab.com/mailman/mailman/-/issues/1050 and added this to the end of /etc/mailman3/mailman-web.py: Q_CLUSTER = { 'workers': 2, 'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5, } However, it does not seem to really reduce the memory footprint. Any other suggestions? Thank you.

2 1

Mailman3 doesn't send Mails to users (Debian12 with Plesk)
by marcus＠mbautze.de 06 Jun '24

06 Jun '24

Hello, i already send this question to the plesk-forum but it seems that nobody there can help me :-( After updating from Debian 10 to 11 to 12, I now have mailman3 running on my server I then converted all lists from Mailman2 to Mailman3 following the instructions from mailman. I can access it via the web interface, manage everything etc. When I register on the web interface, I also receive the corresponding mails from Mailman (forgotten password...) Mails are also arriving, at least mails that are not allowed go into the mails to be approved. The problem, however, is that it does not send out any mails, nor do they appear in the archive. When I look in the Mailman-Log I find: May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost [Errno 111] Connection refused May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: [Errno 111] Connection refused The configuration of Mailman.cfg looks like this: incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 In Mailman manuals I find hints that the transport routes have to be added to the Postfix-config. Doesn't Debian/Plesk do this automatically? Does anyone else have an idea what I need to change to get my mails out? I did the conversion from mailman2 to mailman3 with root because it didn't work with "sudo -u list "m, but the files stored in the file system all belong to list, so that shouldn't be the problem.

9 25

Sending to mangled 'From' addresses.
by hansen 05 Jun '24

05 Jun '24

All, Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. For example, say the mail client captures my address as “Allan Hansen via <listname>” <listaddress> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: “Allan Hansen via <listname>” and, to make it worse, the actual email address, <listaddress>, is often hidden. The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., "Allan Hansen via <listname>" In other words, filtering is done on the name part of the recipient, not the address part. Should I get onto the other list to request this as an enhancement? Yours, Allan

3 3

Sign and encrypt e-mail responses
by Markus Grandpré 04 Jun '24

04 Jun '24

Dear List, is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? Best regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

3 3

Recently active discussions - Hyperkitty
by Sam Darwin 04 Jun '24

04 Jun '24

Hi, Sometimes not sure if it's preferable to open a gitlab issue, or chat on the mailing list. I have run a large archive import into mailman3/hyperkitty. After that's done, waited a day, for scheduled cron jobs to complete. In "All Threads", all the email archives are present. The import worked. In "RECENTLY ACTIVE DISCUSSIONS" on the main page, it says: RECENTLY ACTIVE DISCUSSIONS No discussions this month (yet). Nothing there. That means if I direct users to visit the site, the page, it appears empty. That's too bad. :-) It should display recent emails. What would affect this feature during an archive import? Is it a problem with the import script itself, or with a scheduled cron job, or something else? Would you expect "Recently active discussions" be empty when very recent archives do exist? Thanks, Sam

3 7

import21 detailed usage instructions in 2024
by Keith Christian 03 Jun '24

03 Jun '24

1 Soon, I will be executing the first test imports from Mailman2.1 to Mailman3.9. 2 Planning to copy over the entire production Mailman2.1 to a new directory structure on the Mailman 3.9 machine. 3 Expecting that all .mbox and .pkl files will be present and no special work has to be done to bring them over will a "full" mailman2.1 copy. 4 Can the import21 program find the mailman2.1 .mbox and .pkl files on its own and process them? 5 Other than the mailman2.1 instance being shut down, any other prep that needs to be done? 6 Any special command line parameters to be aware of for import21? 7 Is there a list of troubleshooting steps for commonly encountered migration issues? Thanks. ------------------ Keith

2 1

import21 caused a few mails to be sent out
by Marc SCHAEFER 02 Jun '24

02 Jun '24

Hello, After importing a (big > 3000 subscribers) list with import21, I noticed the following: 36 mails went out from LIST-NAME-bounces to subscribers, but they apparently all bounced. Could those be subscribers that Mailman2 saw bouncing and added the appropriate flag, and Mailman3 sent a probe after the import21? I checked for one of the e-mail address and: Mailman2: - that e-mail has the [X] R flag for "noncourriel" (no delivery) Mailman3: - that e-mail is Delivery mode Regular, Bounces to 0 NB: in MM2 and MM3, all users are in Hold for moderation, that's normal. In addition, there are a few mails in /var/lib/mailman/messages for example that same user: one file, showing a bounce from a remote server. So my questions: 1) is this behaviour to "probe" already disabled addresses normal, and not "port over" the "don't deliver"? 2) why are those messages held in messages/ ? 3) should I then, before running import21, clean the MM2 installation of all those users with [X] R flag? If yes, is there a simple command? Thank you for pointers or help. PS: there was no trafic on that imported mailing-list yet, it's a test.

2 1

Mailman sending email from user@example.com
by dgoldsmith＠sans.org 30 May '24

30 May '24

I have defined an additional SITE in django and the SITE_ID value in /etc/mailman3/settings.py is set to reference that site's ID value. Messages for a list being distributed that are generating certain bounce errors are resulting in email from Mailman 3.x being sent to the list owners from the address user(a)example.com. Is there something else to update in the settings files, Django or the database to make it use the list owner email address tied to the domain of the site? Thanks, David Goldsmith

1 1