May 2024 - Mailman-users - lists.mailman3.org

Issues with a DMARC record leading to message being shunted
by Ralf Hildebrandt 27 Jul '24

27 Jul '24

Hi! Recently a mail was not being distributed via our MM3 instance; I searched the logs and found: Dec 22 04:54:27 2023 (24) ACCEPT: <1d431542-b386-467b-8bf2-305f19ee7eb4(a)somenet.org> Dec 22 04:54:28 2023 (28) Uncaught runner exception: list index out of range Dec 22 04:54:28 2023 (28) Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3.10/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 125, in process authenticate(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/utilities/retry.py", line 44, in f_retry return f(*args, **kwargs) File "/usr/lib/python3.10/site-packages/mailman/handlers/validate_authenticity.py", line 93, in authenticate auth_result = authenticate_message( File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 395, in authenticate_message dmarc_result = check_dmarc(msg, spf_result, dkim_result, dnsfunc=dnsfunc, psddmarc=psddmarc) File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 343, in check_dmarc result, result_comment, from_domain, policy = dmarc_per_from(from_domain, spf_result, dkim_result, dnsfunc, psddmarc) File "/usr/lib/python3.10/site-packages/authheaders/__init__.py", line 90, in dmarc_per_from record, orgdomain = receiver_record(from_domain) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 117, in receiver_record retval = lookup_receiver_record(hostSansDmarc, dnsfunc) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 92, in lookup_receiver_record tags = answer_to_dict(str(result)) File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in answer_to_dict retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} File "/usr/lib/python3.10/site-packages/authheaders/dmarc_lookup.py", line 42, in <dictcomp> retval = {t[0].strip().lower(): t[1].strip().lower() for t in rawTags} IndexError: list index out of range Dec 22 04:54:28 2023 (28) SHUNTING: 1703220868.1418982+b27f5db154375fcd2c418d467172e4aad0d3d57a So the message has been shunted, due to this error. Something with DMARC and tags. So I checked the DMARC record for the sending domain somenet.org. It is "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;mailto:postmaster@somenet.org;ri=3600;fo=1;" which is syntactically incorrect. The extra ";mailto:postmaster@somenet.org" is wrong, I guess the tag "ruf=" is missing here! It should probably read "v=DMARC1;p=none;pct=100;rua=mailto:postmaster@somenet.org;ruf=mailto:postmaster@somenet.org;ri=3600;fo=1;" So, should mm3 somehow "catch" this error somehow? According to the DMARC specs, an syntactically incorrect DMARC record should be ignored / handled as if none were present. -- Ralf Hildebrandt Charité - Universitätsmedizin Berlin Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 ralf.hildebrandt(a)charite.de https://www.charite.de

4 11

Digests not working correctly
by Joel Lord 08 Jun '24

08 Jun '24

So I seem to have problems with both periodic AND size-triggered digests. Size first, this is simpler. Just got one sent out, clearly triggered by a new email getting added to the queued up messages, but the setting for the list is the default 30KB and the digest came out at 23.2 KB. Is it measuring the accumulated queue as size on disk including metadata and filesystem block sizes or something, rather than the size of what the emailed digest will be? Periodic is much more complicated, even to explain. I have the cron job running nightly at 11:00 PM and it certainly seems to be working, except for one really odd thing. The list also definitely has periodic digests enabled in the web UI. This is a very bursty list, so it will go mad with traffic for a few weeks and then will go mostly idle for a month or so. The first digest of a burst is definitely size-triggered, but pretty reliably it has the last few messages from the previous burst in there. So the one I got today had three messages from today and one message from May 4th. But that May 4th message should have gone out at 11:00 PM on May 4th with the daily digest and then gotten flushed from the pending digest queue, right? -- Joel Lord

3 14

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 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

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

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

Have postgresql in the mailman.cfg file but sqlite shows in the mailman info command
by Keith Christian 29 May '24

29 May '24

(venv) [mailman3@localhost-live ~]$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.9.18 (main, Jan 24 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] config file: /opt/mailman3/mailman.cfg db url: sqlite:////opt/mailman3/var/data/mailman.db <<<---------------------------------------- devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Class and url were commented out in the mailman.cfg file, did not recognize postgresql but generated a trace (venv) [mailman3@localhost-live ~]$ grep postgresql /opt/mailman3/mailman.cfg # class: mailman.database.postgresql.PostgreSQLDatabase # url: postgresql://mailman:MYPASSWORD@localhost/mailman Uncommented class and url: class: mailman.database.postgresql.PostgreSQLDatabase <<<---------------------------------------- url: postgresql://mailman:MYPASSWORD@localhost/mailman <<<---------------------------------------- Now I get a stack trace from "mailman info" (venv) [mailman3@localhost-live ~]$ mailman info Traceback (most recent call last): File "/opt/mailman3/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1077, in main with self.make_context(prog_name, args, **extra) as ctx: File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 943, in make_context self.parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1644, in parse_args rest = super().parse_args(ctx, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 1408, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2400, in handle_parse_result value = self.process_value(ctx, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", line 2362, in process_value value = self.callback(ctx, self, value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 228, in initialize initialize_1(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", line 122, in initialize_1 mailman.config.config.load(config_path) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 145, in load self.push(filename, user_config.read()) File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", line 150, in push self._config.push(config_name, config_string) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 582, in push confs = self._getExtendedConfs(conf_name, conf_data) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 615, in _getExtendedConfs _parser_read_file(parser, StringIO(conf_data), conf_filename) File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", line 49, in _parser_read_file parser.read_file(f, source) File "/usr/lib64/python3.9/configparser.py", line 718, in read_file self._read(f, source) File "/usr/lib64/python3.9/configparser.py", line 1085, in _read raise MissingSectionHeaderError(fpname, lineno, line) configparser.MissingSectionHeaderError: File contains no section headers. file: '/opt/mailman3/mailman.cfg', line: 14 <<<---------------------------------------- 'class: mailman.database.postgresql.PostgreSQLDatabase\n' Here is the complete mailman.cfg file: 1 # /etc/mailman3/mailman.cfg 2 # [paths.here] 3 # var_dir: /opt/mailman/mm/var 4 # 5 # [mailman] 6 # layout: here 7 # # This address is the "site owner" address. Certain messages which must be 8 # # delivered to a human, but which can't be delivered to a list owner (e.g. a 9 # # bounce from a list owner), will be sent to this address. It should point to 10 # # a human. 11 # site_owner: user(a)example.com 12 # 13 # [database] 14 # class: mailman.database.postgresql.PostgreSQLDatabase 15 # url: postgresql://mailman:MYPASSWORD@localhost/mailman 16 # 17 # [archiver.prototype] 18 # enable: yes 19 # 20 # # For the HyperKitty archiver. 21 # [archiver.hyperkitty] 22 # class: mailman_hyperkitty.Archiver 23 # enable: yes 24 # configuration: /etc/mailman3/mailman-hyperkitty.cfg 25 # 26 # [shell] 27 # history_file: $var_dir/history.py 28 # 29 # [mta] 30 # verp_confirmations: yes 31 # verp_personalized_deliveries: yes 32 # verp_delivery_interval: 1 33 # Ideas? Thanks.

3 2

Django administration - User permissions
by advorkin＠cs.princeton.edu 29 May '24

29 May '24

Hello, I'm trying to setup users with different permissions. For example: I created a group support with an ability to hyperkitty/mailing list/Can add/change/delete/view mailing list. Unfortunately, the user still does not have an ability to create mailing lists as the option does not exist. It does work when the user is set as "Superuser status". I've also tried giving every possible "available user permissions", but it didn't make a difference. Am I missing something? Thank you!

2 4

Installing Mailman3 under a Python Virtual environment running on RHEL9
by Andy Macheta 29 May '24

29 May '24

Hi, So tried, without much success, to get Postorius working on my Mailman3 server and every internet trick& tip I tried did not work so decided to take a new approach as recommended at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Used this reference: https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ would also work with Red Hat. Fell at the first hurdle with no packages available called "python3-dev" or "python3-venv" Is there anyone that has managed to install a running version of Mailman3 that has a working GUI whether it is on bare metal or Python virtual environment and if so, could they kindly let me know how they did it?? The closest I've come is a running command line version of Mailman3 which is fine for me of course but not for anyone else as they like access via web browser. Thanks in advance, Andy Macheta

4 13

Circumstances in which a subscriber is added to Pending Confirmation list
by David Owen 28 May '24

28 May '24

Hi I wondered if anybody would be able to assist me in my understanding of the Pending Confirmation list, please. In our Mailman mailing list, our Member Policy settings for both Subscription Policy and Un-subscription Policy are set to Open. Therefore we don't require subscribers to confirm their subscription after they submit a request to join our mailing list. Despite this, a number of subscribers seem to be arriving in the Pending Confirmation (Subscriptions pending user confirmation) list. Others correctly arrive in the Members list, as we would expect. All subscription requests are made by the subscriber sending an email to our "join" email address with the subject "subscribe". I've looked at the settings carefully and can't seem to see any that may cause the above behaviour at any time (although I may have missed something of course). Therefore, does anybody know the circumstances in which subscribers to an open mailing list may somehow arrive in the Pending Confirmation list? If I could understand the cause(s) I could then consider ways to manage it or prevent it from happening. Our Mailman installation is hosted centrally in a large organisation so we while we can alter our mailing list's settings in Postorious, we can't alter the source code or similar, so we don't have great room for manoeuvre. Our Postorius version is 1.3.6. Thanks and regards David

1 0