- Mailman-users - lists.mailman3.org

User account issue after importing data from Mailman 2.x server
by dgoldsmith＠sans.org 24 Oct '24

24 Oct '24

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

2 1

Logging subscribes/unsubscribes
by Brian Carpenter 22 Oct '24

22 Oct '24

Does Mailman 3 log subscribes and unsubscribes for each list the way Mailman 2 did? Brian

5 7

Add domain to Mailman, can't create list with that new domain
by Andy Matthews 22 Oct '24

22 Oct '24

I'm testing locally to try and support additional domains. I can add new mailing lists with a domain: announce-123(a)mydomain.com I can't add a new mailing list with an alternate domain: announce-123(a)testing.com Following the documentation for domains I'm able to successfully add the new domain (locally) with the following steps: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… 1. Shell into the mailman server 2. Shell into the mailman Python environment: mailman shell 3. Add a new mailing list. from mailman.interfaces.domain import IDomainManager from zope.component import getUtility manager = getUtility(IDomainManager) manager.add('testing.com') show_domains() # with method from the above documentation URL <Domain testing.com> <Domain mydomain.com> But then when I run a cURL command (from the mailman server) to add a list with that new domain I get an error: $ curl -k -u restadmin:restpass -X POST -H "Content-Type: application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' https://0.0.0.0:8001/3.1/lists {"title": "400 Bad Request", "description": "Domain does not exist: testing.com"} Am I doing something wrong, or missing a step? If not, how do I add support for additional domains such that I can provide mailing list support for that domain?

3 11

OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?
by Bill Oliver 19 Oct '24

19 Oct '24

OK, I think I was clearly in the phase of dealing with errors caused by my attempts to deal with previous errors. So I backed out and did a clean install. Again, the installl seemed to go without a problem. Then: 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" forensic pathologists to discuss cases. 2) I added a couple of users: oliver(a)billoblog.com on the same box as the mailinglist, though on different virtual domains, and william.oliver(a)knoxcounty.org, a local government domain not associated with my box. Results: The welcome message did not get delivered to either address. When I send email from those addresses to tradfp(a)forensicpath.us, I get the following error from both: Your message couldn't be delivered The message you sent to tradfp(a)forensicpath.us couldn't be delivered due to: Recipient email address is possibly incorrect. Further information 5.1.1 <tradfp(a)forensicpath.us>: Recipient address rejected: User unknown in virtual mailbox table If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive. That is when I started going down the dovecot rabbit hole. Here's the (what I think is relevant) part of the mail.cf file: 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 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 virtual_mailbox_base = /var/vmail virtual_minimum_uid = 900 virtual_uid_maps = static:900 virtual_gid_maps = static:900 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains In my previous attempt, I added hash:/opt/mailman/mm/var/data/postfix_lmtp to both virtual_mailbox_maps and virtual_alias_maps, but I haven't done that yet here. I thought I'd ask and make sure I should. Should that be my next step? Thanks, billo

2 3

Debug=False breaks Django/MM3-Login-page
by Stefan Bauer 18 Oct '24

18 Oct '24

Hi folks, I'm trying to hide the custom 404 error messages from Django. ------------------------- Page not found (404) Request Method: GET Request URL: http://......./non-existent-2008020390 Using the URLconf defined in mailman_web.urls, Django tried these URL patterns, in this order: mailman3/ archives/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] accounts/ admin/ postorius/ hyperkitty/ The current path, non-existent-2008020390, didn’t match any of these. You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. ----------------------------- Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error). user-profile/ accounts/logout/ hyperkitty/ Switching back to DEBUG=True brings back accessibility. This is Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] any help is greatly appreciated. Thank you. Stefan

2 1

adding personalized email header/content in mailman 3
by Alex I 17 Oct '24

17 Oct '24

adding personalized email header/content Hello, I'm upgrading from mailman 2.1 and need to have personalized email header and content. In 2.1 eventually (couldn't get custom handler work) I had to modify Decorate.py handler. Basically encrypting email and passing it as a parameter in google required One-click unsubscribe email header link (same in the message body). I tried creating a custom Handler (custom_header.py) in 3.3.19, adding outgoing_pipeline = custom_header in config [mta] section but it doesn't seem to be activating. Thanks

2 6

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