- Mailman-users - lists.mailman3.org

Verification emails 'helo' rejected
by Greg Newby 16 Oct '24

16 Oct '24

Hi friends. I'm now getting a 500 server error upon signing up a new username on the web-based front end. The username is created in the back end, but the verification email does not get sent. This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, PostgreSQL, Postfix Here are the corresponding logfile entries from mailmanweb.log: smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: Helo command rejected: need fully-qualified hostname')} and from mail.log: Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> proto=ESMTP helo=<mail> lists.domain.tld is the domain for Mailman3. I don't know why it's trying to send email from root@. I've seen places where 'localhost' appears in the Mailman settings (settings.py, mailman.cfg, mailman-web.py), and tried changing them to the host's FQDN and restarting mailman3 and mailman3-web, but the problem persists. Suggestions will be appreciated. ~ Greg

4 8

mailmanweb/django?: too many postgresql DB connections
by api＠egartech.com 16 Oct '24

16 Oct '24

Hello, I'm migrating from mailman 2.1 to the latest version (3.3.9) on Almalinux 9 (python 3.19, postgresql 13.16). Have followed the instructions here https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install to perform a clean install on a new VM. Everything seems to be working (well, I just created one list and doing some basic tests). What I have noticed is hundreds of PGsql connections from mailmanweb. Once mailmanweb service is started there are new non-stop DB connections requests (from Django I guess), here is just 1 second from PGsql log: 2024-10-10 12:15:37.112 EDT [3217] DEBUG: forked new backend, pid=3747 socket=10 2024-10-10 12:15:37.113 EDT [3217] DEBUG: server process (PID 3746) exited with exit code 0 2024-10-10 12:15:37.318 EDT [3217] DEBUG: forked new backend, pid=3748 socket=10 2024-10-10 12:15:37.318 EDT [3217] DEBUG: server process (PID 3747) exited with exit code 0 2024-10-10 12:15:37.523 EDT [3217] DEBUG: forked new backend, pid=3749 socket=10 2024-10-10 12:15:37.524 EDT [3217] DEBUG: server process (PID 3748) exited with exit code 0 2024-10-10 12:15:37.728 EDT [3217] DEBUG: forked new backend, pid=3750 socket=10 2024-10-10 12:15:37.729 EDT [3217] DEBUG: server process (PID 3749) exited with exit code 0 2024-10-10 12:15:37.934 EDT [3217] DEBUG: forked new backend, pid=3751 socket=10 2024-10-10 12:15:37.935 EDT [3217] DEBUG: server process (PID 3750) exited with exit code 0 Few minutes later there are around 300 dead (TIME_WAIT) connections to port 5432 like these: tcp 0 0 127.0.0.1:33728 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40392 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:50860 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40254 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40218 127.0.0.1:5432 TIME_WAIT tcp 0 0 127.0.0.1:40110 127.0.0.1:5432 TIME_WAIT I'm totally unfamiliar with Django so not sure where even to look, but that doesn't looks right to me. Thanks

1 1

Database permission problem?
by Bill Oliver 16 Oct '24

16 Oct '24

I have mailman3 installed and mostly configured on a linux machine running ubuntu 24.04. I can use mailmanweb to add and delete mailinglists and users. However, mail is not getting delivered at all. I have both mysql and postgres installed -- I'm using postgres only for mailman, and mysql for dovecot and postfix. Mail, in general, works fine. I'm hosting four virtual domains on this box, and mail to and from all of them to many users gives me no errors. When I add a new user (and thus try to send a welcome message) mail.err log gives me: 2024-10-15T12:40:11.193687-04:00 mail postfix/virtual[960838]: error: open database /opt/mailman/mm/var/data/postfix_lmtp.db: Permission denied I've tried playing with file permissions. I put postfix,mail, and vmail in the mailman group, and tried giving ownership of postfix_domains, postfix_lmtp, and postfix_vmap to user postfix, but that changed nothing. Currently, it sits at: root:/opt/mailman/mm/var/data# ls -l total 36 -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfic_vmap.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfic_vmap.db.db -rw-rw---- 1 postfix mailman 353 Oct 13 07:54 postfix_domains -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfix_domains.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfix_domains.db.db -rw-rw---- 1 postfix mailman 1155 Oct 13 07:54 postfix_lmtp -rw-rw-r-- 1 postfix mailman 0 Oct 15 12:53 postfix_lmtp.db -rw-rw-r-- 1 postfix mailman 12288 Oct 15 12:53 postfix_lmtp.db.db -rw-rw---- 1 postfix mailman 1118 Oct 13 07:54 postfix_vmap So, I'm assuming this is a database permissions error, but I don't know how to fix it. As an aside, my main.cf is below. Any help would be appreciated. billo %cat main.cf smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 #Enable TLS Encryption when Postfix receives incoming emails smtpd_tls_cert_file=/etc/letsencrypt/live/mail.forensicpath.us/fullchai n.pem smtpd_tls_key_file=/etc/letsencrypt/live/mail.forensicpath.us/privkey.p em smtpd_tls_loglevel = 1 smtpd_tls_security_level=may smtpd_tls_loglevel = 1 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache #Enable TLS Encryption when Postfix sends outgoing emails smtp_tls_CApath=/etc/ssl/certs smtp_tls_security_level = may smtp_tls_loglevel = 1 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = mail.forensicpath.us alias_maps = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 #Enforce TLSv1.3 or TLSv1.2 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 mailbox_transport = lmtp:unix:private/dovecot-lmtp smtputf8_enable = no virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf #added 20241009 for mailman hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f #added 20241009 for mailman hash:/opt/mailman/mm/var/data/postfix_vmap virtual_mailbox_base = /var/vmail virtual_minimum_uid = 900 virtual_uid_maps = static:900 virtual_gid_maps = static:900 policyd-spf_time_limit = 3600 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination, check_policy_service unix:private/policyd-spf # Milter configuration milter_default_action = accept milter_protocol = 6 smtpd_milters = local:opendkim/opendkim.sock non_smtpd_milters = $smtpd_milters #Mailman transport stuff transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains

5 12

max_day_to_hold - when in force?
by Wikinaut 15 Oct '24

15 Oct '24

There are quite few discussions (back to 2020) dealing with the variable max_day_to_hold and the (non-) handling of the set value, I found for example Marc's comment https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… : I'm really not sure what you are looking to do, but I can tell you that while the max_days_to_hold list attribute exists and can be set, the actual discarding of held messages older than max_days_to_hold is not implemented. Thus the setting currently does nothing. My question: Are there any plans to bring this into action, so that held messages are really discarded after that number of days? (like it was in mailman2)?

2 1

're' problem is sending messages to queue/shunt for an entire domain
by Greg Newby 15 Oct '24

15 Oct '24

Hi friends. I have multiple domains under MM3 (venv, postfix+postgres, Ubuntu 24.04LTS). Currently at version GNU Mailman 3.3.9 (Tom Sawyer). Following some user complaints, I've discovered that one of the domains isn't working at all. Messages arrive via postfix and are in the MM smtp.log, but then generate a Python error in mailman.log. Other domains are working as usual. The lists in this domain used to work (I can see messages in the archives, and have received copies). But I imported a bunch more MM2 lists since then, and perhaps there is a problem with one of their configurations. Pointers to how to fix this will be appreciated! Here is the error from ~mailman/mm/var/logs/mailman.log: ==> mailman.log <== Oct 13 23:27:34 2024 (365022) Uncaught runner exception: multiple repeat at position 11 Oct 13 23:27:34 2024 (365022) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/runners/incoming.py", line 80, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/rules/banned_address.py", line 40, in check if ban_manager.is_banned(sender): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", line 103, in is_banned re.match(ban.email, email, re.IGNORECASE) is not None): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 167, in match return _compile(pattern, flags).match(string) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile p = _compiler.compile(pattern, flags) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile p = _parser.parse(p, flags) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 979, in parse p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse raise source.error("multiple repeat", re.error: multiple repeat at position 11 Followed by a message that it's going to queue/shunt: Oct 13 23:15:25 2024 (365022) SHUNTING: 1728886525.4656847+d1a03bf710a246d029a087eabd40bed11c1af4b5 ... where it stays. Delivery never happens. I've tried with listname(a)lists.domain.tld as well as listname-owner(a)lists.domain.tld. The lists in the domain seem to be set up properly -- they used to work fine! I am suspicious the problem happened when I imported some other lists, but those imports didn't cause any errors. I've done the usual sequence of restarting mailman services, rebooting the server, double-checking the configuration files, and reviewing the list settings. Thanks for your help! ~ Greg

2 2

Search function returning results from another list
by Marco van Tol 15 Oct '24

15 Oct '24

Hi there, We have several lists on our list server here, and noticed that if we do this: - go to the archive of public list x - type in "minutes" in the search bar If will: - show a screen: list-x search results for query "minutes" - have 3 results in there for another private list - show a message that you need to login to view the message if you click on one Our current mailman core version is: 3.3.9 Our current hyperkitty version is: 1.3.10 Our index engine is: xapian_backend.XapianEngine Does this make sense? Thanks! Marco van Tol RIPE NCC

1 2

Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails
by francesd919＠gmail.com 12 Oct '24

12 Oct '24

Hi everyone, I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. These emails mentioned that the subscription was disabled due to bounce score. Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. I have some questions: 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. 3. What could have cuased functioning emails to bounce and therefore being disabled? Thank you in advance! Frances 3.

2 1

mailman changeaddress: Address already exists; can't change
by joelbrownstein＠computer.org 12 Oct '24

12 Oct '24

Hi, We migrated ~100 lists from mailman2 to mailman3 (very nice!) including > 6000 distinct email addresses ("subscribers"). I would like to run the mailman changeaddress command to do a global change of email for a member that moved. But they have other subscriptions using their new email, so both the old and new address are migrated to mailman3 as distinct "members", which prevents the mailman changeaddress from making the change with error: $ mailman changeaddress "EMAIL_1" "EMAIL_2" Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS Try 'mailman changeaddress -h' for help. Error: Address "EMAIL_2" already exists; can't change. Is there a workaround? Thanks, Joel

2 1

MM3 error on moderation request
by Odhiambo Washington 11 Oct '24

11 Oct '24

MM3 - 3.3.10, Postorius 1.3.13. After receiving the notification to attend to a moderation request: ``` At your convenience, visit https://mm3-lists.kictanet.or.ke/mm/lists/kictanet.lists.kictanet.or.ke/hel… to approve or deny the request(s). ``` Upon visiting the link I ended up with a server error. mailmanweb.log has the below to say: ``` [ERROR] [2024-10-10 12:29:15,905] [log] 809040 139858772735552 Internal Server Error: /mm/lists/kictanet.lists.kictanet.or.ke/held_messages Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1026, in find_library return parser.libraries[name] ~~~~~~~~~~~~~~~~^^^^^^ KeyError: 'humanize' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/contrib/auth/decorators.py", line 23, in _wrapper_view return view_func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/postorius/auth/decorators.py", line 63, in wrapper return fn(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/postorius/views/list.py", line 889, in list_moderation return render(request, 'postorius/lists/held_messages.html', context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader.py", line 61, in render_to_string template = get_template(template_name, using=using) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader.py", line 15, in get_template return engine.get_template(template_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/backends/django.py", line 33, in get_template return Template(self.engine.get_template(template_name), self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/engine.py", line 175, in get_template template, origin = self.find_template(template_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/engine.py", line 157, in find_template template = loader.get_template(name, skip=skip) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loaders/cached.py", line 57, in get_template template = super().get_template(template_name, skip) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loaders/base.py", line 28, in get_template return Template( ^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 154, in __init__ self.nodelist = self.compile_nodelist() ^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 200, in compile_nodelist return parser.parse() ^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 513, in parse raise self.error(token, e) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 511, in parse compiled_result = compile_func(self, token) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/loader_tags.py", line 293, in do_extends nodelist = parser.parse() ^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 513, in parse raise self.error(token, e) File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/base.py", line 511, in parse compiled_result = compile_func(self, token) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1088, in load lib = find_library(parser, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/django/template/defaulttags.py", line 1028, in find_library raise TemplateSyntaxError( django.template.exceptions.TemplateSyntaxError: 'humanize' is not a registered tag library. Must be one of: account admin_list admin_modify admin_urls allauth bootstrap_tags cache compress d_gravatar date_helpers debugger_tags decorate gravatar highlight highlighting hk_generic hk_haystack i18n indent_text l10n log markdown membership_helpers more_like_this nav_helpers p_gravatar pagination postorius_helpers rest_framework socialaccount static syntax_color tz widont [WARNING] [2024-10-10 12:29:16,384] [log] 809040 139858704070336 Not Found: /mc/compose ``` How to fix? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 2

Two trivial questons:
by Bill Oliver 10 Oct '24

10 Oct '24

First: Last night I got everything installed and, I think, working. Unfortunately, I forgot to write down the name and password of the superuser I created. I know what I put in as password, but I cant' remamber the name of the superuser. I know I could just create another superuser with "mailmanweb createsuperuser" but I was wondering if there was a "mailmanweb" command for *listing* superusers. If not, I'll just make another superuser... Second: I have the "example.com" error in the login screen. The instructions state that this is a problem with making SITE_ID=1. Okay, but I don't know what to change it to. I tried SITE_ID=2 on a lark and everything broke, and the instruction say not to do SITE_ID=0. Apparently it has to be an integer (I also tried putting in site name and got that error). So... where do I change it? Thanks! billo

1 3