- Mailman-users - lists.mailman3.org

Posterious membership listing for non-owner/moderators?
by Duane Raymond 11 Mar '21

11 Mar '21

Hi, I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. (as usual before asking the question I explored a lot and searched the archives/documentation). Cheers, Duane

2 2

Setting for archiving multi email domains?
by Duane Raymond 11 Mar '21

11 Mar '21

Hi again, I have a Debian-postfix-postgres-nginx-Hyperkitty-Postorius setup with a primary domain (e.g. primarydomain.com) and several 'secondary' domains used for email lists (e.g. emaillistA.com and emaillistB.com). When sending emails to a list using the primarydomain.com address, the email is received, sent to subscribers and archived properly. But when it is sent to one of the secondary domains like tes(a)emaillistA.com - the email doesn't seem to be sent and isn't archived - despite it being set to be. What I've tried so far (after searching these archives and looking at the documentation) is to: 1) Adding emaillistA.com and emaillistB.com to the MAILMAN_ARCHIVER_FROM setting in the settings_local.py file (and then restart mailman) 2) Adding emaillistA.com and emaillistB.com to the mydestination setting in the postfix main.cf file (and the restarting postfix). ...I even tried adding to /etc/hosts 127.0.0.1 emaillistA.com and 127.0.0.1 emaillistB.com but removed it as it didn't seem appropriate there. Does anyone have any hits of what else I need to configure to get it working for these 'secondary' email domains? Cheers, Duane

4 24

Backups & disaster recovery of mailman3
by David Partain 08 Mar '21

08 Mar '21

Hi, So now I have a running mailman3 installation. Whew... Is there documentation of things like thorough backups and disaster recovery? I haven't yet found it. Backups: Obviously, I understand that I need to have datbase (mysql, in my case) dumps, and I'll have file system backups onto something that our IT folks will backup. Is there more I should think of? Disaster recovery: So, let's say my server (which is cloud-y) gets trashed and I need to get mailman back on a new server. Is this process described somewhere? My kind thanks to you all for listening :) Cheers, David

2 1

Email Commands
by Brian Carpenter 07 Mar '21

07 Mar '21

Is there a list of email commands on a website somewhere that you can use with Mailman 3? -- Brian Carpenter Harmonylists.com Emwd.com

2 1

Importing issue from mailman2 to mailman3
by David Partain 07 Mar '21

07 Mar '21

Hi, I'm in the process of moving 1400-ish lists from a very old mailman2 installation to an installation on Ubuntu 18.04 with the version of mailman3 packaged for that distro. (Yes, that was a mistake, but I'm committed at this point.) I'm doing this import as per: sudo -u list mailman import21 somelist@one-of-the-domains<mailto:somelist@one-of-the-domains> /tmp/lists/somelist/config.pck where /tmp/lists includes all of the list configs from the old installation. Most of it's going fine, as best I can see. However, I get exceptions on some lists that look like this: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1182, in _execute_context context) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 470, in do_execute cursor.execute(statement, parameters) File "/usr/local/lib/python3.6/dist-packages/pymysql/cursors.py", line 163, in execute result = self._query(query) File "/usr/local/lib/python3.6/dist-packages/pymysql/cursors.py", line 321, in _query conn.query(q) File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 505, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 724, in _read_query_result result.read() File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 1069, in read first_packet = self.connection._read_packet() File "/usr/local/lib/python3.6/dist-packages/pymysql/connections.py", line 676, in _read_packet packet.raise_for_error() File "/usr/local/lib/python3.6/dist-packages/pymysql/protocol.py", line 223, in raise_for_error err.raise_mysql_exception(self._data) File "/usr/local/lib/python3.6/dist-packages/pymysql/err.py", line 107, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.DataError: (1406, "Data too long for column 'info' at row 1") My assumption is that what's in the "Info" field on the old mailman2 config is simply too long. Is that correct? In that case, I suppose the right thing is to (1) edit each one, reducing the size, which'll create a new config.pck, (2) pull it over to the new machine, and (3) run the import again. Seem reasonable? Cheers, David

2 2

[Django] ERROR (EXTERNAL IP): Service Unavailable
by dancab＠caltech.edu 05 Mar '21

05 Mar '21

I've imported a list from Mailman2 and had the owner send a message for testing purposes. His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. However if we attempt to view the message in Postorius web UI then an error is thrown. In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages Does "Service Unavailable" mean I'm missing something in the configuration? Thanks for your help. ---- Dan Caballero

3 16

postfix malformed address with confirm replies
by Stephen Willey Mats Mats 04 Mar '21

04 Mar '21

I’m getting bounces back from postfix (553 5.1.3 Error: malformed address) for my confirm replies. I found a similar issue in this lists’ archives back in 2017 but that issue was supposedly fixed in version 3.2 I’m running the current docker containers. I’m pretty sure I have all of the mailman settings in postix: " # Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains " the entries in /opt/mailman/core/var/data/postfix_lmtp look like they should match /^matsmats-mm3-test1(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-bounces(\+.*)?(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-confirm(\+.*)?(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-join(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-leave(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-owner(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-request(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-subscribe(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 /^matsmats-mm3-test1-unsubscribe(a)mm3\.aca-aws\.s\.uw\.edu$/ lmtp:[172.19.199.2]:8024 thanks, steve > On Feb 26, 2021, at 14:08:54 PST, Mail Delivery System <MAILER-DAEMON(a)ip-172-31-18-222.us-west-2.compute.internal> wrote: > > This is the mail system at host ip-172-31-18-222.us-west-2.compute.internal. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > > The mail system > > <matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu>: > host 172.19.199.2[172.19.199.2] said: 553 5.1.3 Error: malformed address > (in reply to RCPT TO command) > Reporting-MTA: dns; ip-172-31-18-222.us-west-2.compute.internal > X-Postfix-Queue-ID: E144B8BC3C5 > X-Postfix-Sender: rfc822; stephen.s.w.matsmats(a)gmail.com > Arrival-Date: Fri, 26 Feb 2021 14:08:54 -0800 (PST) > > Final-Recipient: rfc822; matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu > Original-Recipient: rfc822;matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu > Action: failed > Status: 5.1.3 > Remote-MTA: dns; 172.19.199.2 > Diagnostic-Code: smtp; 553 5.1.3 Error: malformed address > > From: Steve Mats Mats <willey(a)selby.com> > Subject: Re: Your confirmation is needed to join the matsmats-mm3-test1(a)mm3.aca-aws.s.uw.edu mailing list. > Date: February 26, 2021 at 2:08:52 PM PST > To: matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu > > > > >> On Feb 26, 2021, at 11:41:54 PST, matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu wrote: >> >> Email Address Registration Confirmation >> >> Hello, this is the GNU Mailman server at mm3.aca-aws.s.uw.edu. >> >> We have received a registration request for the email address >> >> willey(a)teamd.org >> >> Before you can start using GNU Mailman at this site, you must first confirm >> that this is your email address. You can do this by replying to this message. >> >> Or you should include the following line -- and only the following >> line -- in a message to matsmats-mm3-test1-request(a)mm3.aca-aws.s.uw.edu: >> >> confirm d6f77a2572ef55a8b2c4ca0d77de8493fbb55856 >> >> Note that simply sending a `reply' to this message should work from >> most mail readers. >> >> If you do not wish to register this email address, simply disregard this >> message. If you think you are being maliciously subscribed to the list, or >> have any other questions, you may contact >> >> matsmats-mm3-test1-owner(a)mm3.aca-aws.s.uw.edu > > >

4 9

Set Postorius interface locale
by Duane Raymond 04 Mar '21

04 Mar '21

Hi everyone, Thanks to Brian I'm up and running with my migrated mailman3 lists and am now starting to get into customising the interface (styling and content). I've been trying to figure out how to set/change the Postorius locale - I specifically want to change some text strings on the info page without breaking the i18n mechanisms. I've worked with po and mo files before, so changing and compiling them isn't a problem. The problems I've encountered so far are: 1) Where do I set the local of the Postorius interface? 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Am I looking at this all wrong? The documentation doesn't seem to have any info about this and yet the mechanisms seem to be there. Once I learn more I'm quite keen to start working on improving the documentation based on what I learn. Cheers, Duane

3 4

Moderation emails
by peter＠chubb.wattle.id.au 04 Mar '21

04 Mar '21

Hi Folks, Whenever a non-member posts to a members-only list, the owners (because I haven't set any moderators) get a 3-part MIME message, from the xxx-owner email address. The first part is the template from .../mailman/templates/en/list:admin:action:post.txt The second part is a message/rfc822 copy of the held message. The third part is another message/rfc822 part that says, If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply. This is really confusing, as replying to the whole message will go to the '-owner' not the '-request' address, which will neither discard nor authorise the message, and will not contain the subject: heading from the encapsulated message. Is there any easy way, either to turn off generation of the third message, or make it so that acting on the message (hitting reply in your email client) will actually discard the message? Peter C

2 1

postorius / adjusted settings menu
by Andreas Barth 03 Mar '21

03 Mar '21

Hi together, I want to adjust the settings menu to reduce to the options really needed. The easiest way would be to edit src/postorius/views/list* but I don't think that's a good idea. So what comes to my mind is to have some variable in the configuration that contains the menu items and - if set - the submenus. E.g. the following: { 'list_identity': ['!gateway_to_mail', '!gateway_to_news', '!linked_newsgroup', '!newsgroup_moderation', '!nntp_prefix_subject_too' ], 'automatic_responses', 'alter_messages', 'dmarc_mitigations', 'digest', 'message_acceptance', 'archiving', 'subscription_policy', 'bounce_processing' } would express: default menu and just remove the mentioned items. Of course, something like ['advertised', 'description', 'info', 'display_name', 'subject_prefix'] would work as well. Resorting should also be possible, so something like { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } would give a very small list of items to select from. What do you think about the idea? Andi

2 1