- Mailman-users - lists.mailman3.org

Something wrong with my Hyperkitty base_url?
by Andrew Hodder Oct. 2, 2017

Oct. 2, 2017

Finally have everything stood up and working, except for HyperKitty mailman plugin. I'm getting a path issue of sorts I can see in the archiver.log (have it set to debug log level in the mailman core): Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): File "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv3/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <h1>Not Found</h1><p>The requested URL /archives/api/mailman/archive was not found on this server.</p> My base_url in the mailman-hyperkitty.cfg: base_url: http://localhost:8002/archives I've tried changing localhost to the FQDN but that just gives different errors (where it can't even attempt to exchange the secret, so I know at least that part is working. Just this '/archives/api/mailman/archive' path I'm head scratching at. I've tried removing the /archives off the end, no change though. Any thoughts/help would be appreciated, thanks! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541

2 4

question about recommended postfix configuration
by Marc Sluiter Oct. 2, 2017

Oct. 2, 2017

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. This is recommended: 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 This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. My first change then was to use “relay_recipient_maps” instead of “local_recipient_maps”, because the domains were also added to the relay configuration "relay_domains". That worked. But then I noticed warnings by postfix about having the same domain in “virtual_mailbox_domains” and “relay_domains”. Made sense again because I used the same domain in my “normal” mail setup (with “virtual_mailbox_domains”) and in mailman. So finally I ended up with adding the mailman files to “virtual_mailbox_domains” and “virtual_mailbox_maps” instead of “relay_domains” and “local_recipient_maps”. Do my findings and changes make sense to you? Or do I miss something important? Good thing is that at least “transport_maps” worked for whatever configuration I used :) Thanks and greetings, Marc

2 1

default language ignored
by Marc Sluiter Oct. 2, 2017

Oct. 2, 2017

Hi, one last question for now: how do switch the language of the mails sent by mailman? I have this in my configuration, but without effect: [language.de] charset: iso-8859-1 [language.de] description: German [language.de] enabled: yes [mailman] default_language: de Is it also possible to change the language for a single list? Greetings, Marc

2 1

Confirmation email bounces because of listname+something@example.com
by thor.rustad＠gmail.com Oct. 2, 2017

Oct. 2, 2017

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td…. Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 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 unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 <abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=<me(a)mydomain.com> to=<abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated.

2 1

Confirmation email bounces because of listname+something@example.com
by Thor Atle Rustad Oct. 2, 2017

Oct. 2, 2017

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td… . Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 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 unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 < abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=< me(a)mydomain.com> to=< abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated. Thor

2 1

"Private archives" aren't private
by Simon Liebold Sept. 29, 2017

Sept. 29, 2017

Hello, #129 says that private lists are visible in the archive overview only but "archives aren't displayed". However, I can browse a private list's archives and read the mail text while not logged in. Shouldn't the private archive be hidden from anonymous users? Simon

6 10

"spoofing" mailing list address
by Dmitry Makovey Sept. 29, 2017

Sept. 29, 2017

Hi, We're trying to migrate from 2.1.x to 3.1. In the process we want to modify old setup in which mailing lists were part of our normal mail domain (so both user accounts and ML would be under @x.stanford.edu) in new scenario we want to move ML into @lists.x.stanford.edu, yet preserve addressing compatibility with old naming scheme. To that end we thought of making following setup: list(a)x.stanford.edu -postfix:alias-> list(a)lists.x.stanford.edu however in this setup users will receive mail from the "unknown" domain for them so any filtering they've done will break. Is there a configuration change we can make for those old ML to spoof old ML emails? so they would look as if they came from list(a)x.stanford.edu ? -- Sr System and DevOps Engineer SoM IRT

1 0

Mailman only send some release messages to the subscribers
by Henrik Rasmussen Sept. 28, 2017

Sept. 28, 2017

I have three list admins each maintaining one list, thus three lists: E, H and S. All reports that some mails they release from Held messages are sent, some isn't. In the logs (Mailman smtp.log and postfix log I can confirm that at least one of the lists (E) sent out another message to 559 recips at Sep 26 09:31:12 201 (UTC+2) so something is working. The admin of list E explains that she have released mails that came out, but some mails isn't sent when she reases them. Among others a mail she released Sep 26 09:38. I can also see in the Mailman Postfix log that Mailman received a mail from the Admin's e-mail address sender(a)foo.bar. Sep 26 09:38:49 postfix postfix/smtpd[5527]: D8E6D1109026: client=gateway[172.19.199.1] Sep 26 09:38:49 postfix postfix/cleanup[6076]: D8E6D1109026: message-id=<E7657360D6CFE64DBAC4E5D158511918873690FB(a)mailserver.foo.bar> Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: from=<sender(a)foo.bar>, size=19589, nrcpt=1 (queue active) Sep 26 09:38:49 postfix postfix/lmtp[6077]: D8E6D1109026: to=<s(a)listserver.foo.bar>, relay=172.19.199.2[172.19.199.2]:8024, delay=0.03, delays=0.01/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 26 09:38:49 postfix postfix/qmgr[139]: D8E6D1109026: removed I cannot find the mail-id in the Mailman smtp.log, however in the smtp.log I found that the mail was received Sep 26 09:38:49 2017 (32) Peer: ('172.19.199.5', 49238) Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) handling connection Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'LHLO mailgateway.foo.bar' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'MAIL FROM:<sender(a)foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) sender: sender(a)foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'RCPT TO:<s(a)listserver.foo.bar>' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) recip: s(a)listserver.foo.bar Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'DATA' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) Data: b'QUIT' Sep 26 09:38:49 2017 (32) ('172.19.199.5', 49238) connection lost Sep 26 09:38:49 2017 (32) Connection lost during _handle_client() I don't see any release of the held mail not that it was sent out. Two hours later I see a a log message about a notification mail to the admin that another mail had been held, but not anything about the released mail neither in thge smtp.log nor the postfix log. I don't know why it only works sometimes. -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark

1 2

mailman-cli tools
by Dmitry Makovey Sept. 27, 2017

Sept. 27, 2017

I've come across mailman-cli docs: http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… yet I cannot figure out what's the official source for the installation. Rabbit hole of links lead me to https://github.com/rajeevs1992/mailmancli which suggests: sudo pip install mailman.client and that doesn't work. I also did: pip install mailmanclient in hopes that it comes with CLI tools, but it looks like it is only the library. Am I looking in wrong places or is it that mailman3 cli tools are "not there"? -- Sr System and DevOps Engineer SoM IRT

3 5

HyperKitty: Thread matching query does not exist
by C. R. Oldham Sept. 26, 2017

Sept. 26, 2017

Greetings, I have an active list for which I am trying to debug some deliverability issues. When a user tells me that folks aren't getting their postings, I check the archives first. In this case, I am getting a traceback saying "thread matching query does not exist" when I try to go to the HyperKitty page for the list. How can I debug this? I am using Mailman 3 via the Docker containers documented here: https://asynchronous.in/docker-mailman/ The container versions appear to be 0.1. --cro

3 3