- Mailman-users - lists.mailman3.org

MM3 vs. Sympa
by Tom Browder Oct. 21, 2018

Oct. 21, 2018

I still haven’t gotten around to getting a new MM3 service up and running, and now I’m looking at Sympa. I’ve seen a few comparisons of the two systems on the net, but the ones I’ve seen are for announcement lists only. I did see one university that did a study of list managers to replace Listproc and chose Sympa. I must admit my short-lived MM2 experience (used for my social sites for my high school and college classmates) seven years ago wasn’t the best was for two reasons: (1) no duplication of list names even for different domains and (2) it’s written in Python (instead of Perl). But, thanks to much help from Mark, I did get it runnng. I think it would be running today but it failed after about a year when Gmail (whose sntp server I was using) stopped allowing that, and I just didn’t know enough to get around the situation and had too much else to do. I waited expectantly for MM3 to come out and was ready to try again, but the separation of a formerly-integrated system into several systems was a bit daunting. Now I’m considering using Sympa: it’s coded in Perl, it’s monolithic, and it can support identical list names for different domains, so I am leaning in that direction. Before I go, I would appreciate anyone giving me a good reason to stay with MM (besides excellent support and a welcoming community—one which is a member of an unfortunately small group of such communities). Thanks so much. Best regards, -Tom

4 5

Difficulties setting up MM3 with Postfix MTA in Docker Environment: Invalid EHLO domain name & Authentification as lists.local
by Niklas Frühauf Oct. 21, 2018

Oct. 21, 2018

Hi everyone, I managed to setup mailman using the maxking/mailman-* docker containers, connected to a postfix/dovecot mailserver and a mysql database. The mail domain is @mail.local, mailman is reachable at lists.local. I can see the mailman UI fine, its connection to the database is working as well, the only things that’s not working is the initial login: When I try to login with the correct credentials of the superuser I added, I get An error occurred while processing your request. To me it seems like mailman is trying to authenticate as “lists.local” or “mail.local” or “localhost” to postfix (which of course isn’t working), then issues a EHLO/HELO to postfix which is not a FQDN. So I guess the latter issue could be resolved by providing a FQDN by mailman. These are the logfiles from the period: mail | Oct 21 11:15:07 mail postfix/postscreen[1862]: CONNECT from [172.18.18.8]:49288 to [172.18.18.254]:25 ldap_1 | 5bcc5fc1 conn=1000 fd=12 ACCEPT from IP=172.18.19.8:49252 (IP=0.0.0.0:389) ldap_1 | 5bcc5fc1 conn=1000 op=0 BIND dn="cn=admin,dc=..." method=128 ldap_1 | 5bcc5fc1 conn=1000 op=0 BIND dn="cn=admin,dc=..." mech=SIMPLE ssf=0 ldap_1 | 5bcc5fc1 conn=1000 op=0 RESULT tag=97 err=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=1 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=lists.local)" ldap_1 | 5bcc5fc1 conn=1000 op=1 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=1 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=2 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=lists.local)" ldap_1 | 5bcc5fc1 conn=1000 op=2 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=2 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=3 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@lists.local)(mailalias=*@lists.local))" ldap_1 | 5bcc5fc1 conn=1000 op=3 SRCH attr=mail ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fc1 conn=1000 op=3 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=4 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=mail.local)" ldap_1 | 5bcc5fc1 conn=1000 op=4 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=4 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=5 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=mail.local)" ldap_1 | 5bcc5fc1 conn=1000 op=5 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=5 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=6 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@mail.local)(mailalias=*@mail.local))" ldap_1 | 5bcc5fc1 conn=1000 op=6 SRCH attr=mail ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fc1 conn=1000 op=6 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=7 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=lists.local)" ldap_1 | 5bcc5fc1 conn=1000 op=7 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=7 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=8 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=lists.local)" ldap_1 | 5bcc5fc1 conn=1000 op=8 SRCH attr=mail ldap_1 | 5bcc5fc1 conn=1000 op=8 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fc1 conn=1000 op=9 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@lists.local)(mailalias=*@lists.local))" ldap_1 | 5bcc5fc1 conn=1000 op=9 SRCH attr=mail ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fc1 <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fc1 conn=1000 op=9 SEARCH RESULT tag=101 err=0 nentries=0 text= mail | Oct 21 11:15:13 mail postfix/postscreen[1862]: PASS OLD [172.18.18.8]:49288 mail | Oct 21 11:15:13 mail postfix/smtpd[1873]: connect from srv-docker_mailman-web_1.srv-docker_frontend[172.18.18.8] mail | Oct 21 11:15:17 mail postfix/postscreen[1862]: warning: dnsblog reply timeout 10s for list.dnswl.org mail | Oct 21 11:15:27 mail postfix/dnsblog[1866]: warning: dnsblog_query: lookup error for DNS query 8.18.18.172.list.dnswl.org: Host or domain name not found. Name service error for name=8.18.18.172.list.dnswl.org type=A: Host not found, try again ldap_1 | 5bcc5fdf conn=1000 op=10 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=lists.local)" ldap_1 | 5bcc5fdf conn=1000 op=10 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=10 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=11 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=lists.local)" ldap_1 | 5bcc5fdf conn=1000 op=11 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=11 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=12 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@lists.local)(mailalias=*@lists.local))" ldap_1 | 5bcc5fdf conn=1000 op=12 SRCH attr=mail ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fdf conn=1000 op=12 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=13 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=localhost)" ldap_1 | 5bcc5fdf conn=1000 op=13 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=14 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=localhost)" ldap_1 | 5bcc5fdf conn=1000 op=14 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=14 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=15 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@localhost)(mailalias=*@localhost))" ldap_1 | 5bcc5fdf conn=1000 op=15 SRCH attr=mail ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fdf conn=1000 op=15 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=16 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(mail=lists.local)" ldap_1 | 5bcc5fdf conn=1000 op=16 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=16 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=17 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(?mailGroupMember=lists.local)" ldap_1 | 5bcc5fdf conn=1000 op=17 SRCH attr=mail ldap_1 | 5bcc5fdf conn=1000 op=17 SEARCH RESULT tag=101 err=0 nentries=0 text= ldap_1 | 5bcc5fdf conn=1000 op=18 SRCH base="ou=users,dc=..." scope=2 deref=0 filter="(|(mail=*@lists.local)(mailalias=*@lists.local))" ldap_1 | 5bcc5fdf conn=1000 op=18 SRCH attr=mail ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mail) not indexed ldap_1 | 5bcc5fdf <= mdb_substring_candidates: (mailalias) not indexed ldap_1 | 5bcc5fdf conn=1000 op=18 SEARCH RESULT tag=101 err=0 nentries=0 text= mail | Oct 21 11:15:43 mail policyd-spf[1886]: prepend Received-SPF: Temperror (mailfrom) identity=mailfrom; client-ip=172.18.18.8; helo=c98c668820fd; envelope-from=postorius(a)lists.local; receiver=<UNKNOWN> mail | Oct 21 11:15:43 mail postfix/smtpd[1873]: NOQUEUE: reject: RCPT from srv-docker_mailman-web_1.srv-docker_frontend[172.18.18.8]: 504 5.5.2 <c98c668820fd>: Helo command rejected: need fully-qualified hostname; from=<postorius(a)lists.local> to=<niklas.fruehauf(a)mail.local> proto=ESMTP helo=<c98c668820fd> mail | Oct 21 11:15:43 mail postfix/postscreen[1862]: CONNECT from [172.18.18.8]:49304 to [172.18.18.254]:25 mail | Oct 21 11:15:43 mail postfix/postscreen[1862]: PASS OLD [172.18.18.8]:49304 mail | Oct 21 11:15:43 mail postfix/smtpd[1903]: connect from srv-docker_mailman-web_1.srv-docker_frontend[172.18.18.8] proxy_1 | 172.18.18.1 - - [21/Oct/2018:11:16:13 +0000] "POST /accounts/login/ HTTP/1.1" 500 1102 "https://lists.local/accounts/login/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36" "-"

3 2

footer message
by Abhijith PA Oct. 19, 2018

Oct. 19, 2018

Hello. Is there any way to enable footer for some lists at the same time disable for lists. I maintain an mailman3 instance and some of the lists in it need the footer message well some not. Regards, Abhijith.

3 5

dkim failing
by Abhijith PA Oct. 16, 2018

Oct. 16, 2018

Hello. I am seeing dkim fail in mail that people send to lists /dkim=fail reason="signature verification failed"/ but it is not happening when the list solely sending mail to subscribers (like digest, or subscribe/unsubscribe messages etc). I recently added a new domain to the mailman3. After this I started noticing this issue. Any help ?

2 1

dkim failing
by Abhijith PA Oct. 16, 2018

Oct. 16, 2018

Hello. I am seeing dkim fail in mail that people send to lists /dkim=fail reason="signature verification failed"/ but it is not happening when the list solely sending mail to subscribers (like digest, or subscribe/unsubscribe messages etc). I recently added a new domain to the mailman3. After this I started noticing this issue. Any help ? Thanks Abhijith PA

2 1

Change digest frequency and default threshold
by Henrik Rasmussen Oct. 12, 2018

Oct. 12, 2018

When creating a new list in Mailman 3, the Digest Size Threshold is set to 30KB, which is not much in my opnion. 1) How do I set another default for Digest Size Threshold for new lists. 2) How do I change the default for existing lists When Digest Size Threshold is not reached, mails seems to be sent according to digest_volume_frequency': which is set to 'monthly'. The web interface doesn't seem to have a setting for this. How do I change this setting, both on a single list and the default for new lists? Henrik Rasmussen

2 9

Can't remove footer(s)
by Henrik Rasmussen Oct. 11, 2018

Oct. 11, 2018

I have a problem removing the footer(s) from a list imported from MM2.1. I have been testing by entering my message in Hyperkitty (the list forum). I an aware about the double footer issue[1], and I am aware that footers are cached, but I have removed the footer files according to [2], run Mailman shell according to [3], restarted the Mailman (Mailman core, Mailan web, Postgres database and postfix). Did I miss something in order to remove the footers? [1] https://gitlab.com/mailman/mailman/issues/407 [2] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… [3] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I'm running Docker-Mailman (Mailman version 3.2.0a1). -- Henrik Rasmussen

2 5

Archiving error
by Enrique Terrazas Oct. 5, 2018

Oct. 5, 2018

Hello, I'm hoping someone can help me configure hyperkitty correctly. I've got mailman3 installed and working. I created a test list and can send/receive, moderate message. However, archiving does not seem to be working. Below is a copy of my (sanitized) hyperkitty.cfg file and settings.py file(edited) along with the errors being logged to mailman.log hyperkitty.cfg ----- # Mailman-Hyperkitty Archiver plugin [general] base_url: http://localhost:8002/ api_key: ----- settings.py # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = '' MAILMAN_REST_API_PASS = '' MAILMAN_ARCHIVER_KEY = '' MAILMAN_ARCHIVER_FROM = ('my.host.name', 'myIPaddress', '127.0.0.1', '::1') ------ This is the error being sent to maillog.log ------ Oct 05 01:54:59 2018 (15127) Exception in "hyperkitty" archiver Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 171, in _new_ conn (self._dns_host, self.port), self.timeout, **extra_kw) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 79, in c reate_connection raise err File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/util/connection.py", line 69, in c reate_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen chunked=chunked) File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request conn.request(method, url, **httplib_request_kw) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1239, in request self._send_request(method, url, body, headers, encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1285, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1234, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1026, in _send_output self.send(msg) File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 964, in send self.connect() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 196, in connect conn = self._new_conn() File "/opt/mailman/mailman/lib64/python3.6/site-packages/urllib3/connection.py", line 180, in _new_conn self, "Failed to establish a new connection: %s" % e) urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f0ba1c22048>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: ------ Thanks in advance, Enrique J. Terrazas

3 5

Hyperkitty 1.1.1 to HyperKitty 1.2.1
by Thomas G Oct. 5, 2018

Oct. 5, 2018

Hi, I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh install in Mailman3.2. I didn't found how migrate the archives. From : HyperKitty - Version: 1.1.1 - Python2.7 To : HyperKitty - Version: 1.2.1 - Python3.5 I exported a mbox from hyperkitty (web interface) and tried to re-import it, without result. """""""""""""""""""""""""""""""""""""""" xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to listedetests(a)hatlab.fr Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the 'manage.py update_index_one_list listedetests(a)hatlab.fr' command. """""""""""""""""""""""""""""""""""""" The database stay empty (and web interface): """""""""""""""""""""""""""""""""""""" mailmandbnameprod=# select * from hyperkitty_email; id | message_id | message_id_hash | subject | content | date | timezone | in_reply_to | archived_date | thread_depth | thread_order | mailinglist_id | parent_id | sender_id | thread_id | sender_name ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- (0 rows) """""""""""""""""""""""""""""""""""""" Any idea to do this importation ? Thanks !

3 7

Proper permissions for mailman installation under home directory, with layout: local
by Eric Abrahamsen Oct. 3, 2018

Oct. 3, 2018

I recently upgraded my server from Ubuntu 16.04 to 18.04, and have hit some snags in the process. I've had my mailman3 installation under my home directory, running as my own user, without too many problems. var_dir was set to something in my home directory. Recently, while tracking down some weird behavior, I realized that with this sort of setup I'm supposed to use "layout: local", and that previously I'd had a sort of weird half-way installation where some things were kept in my /home/<me>/sites/mailman directory, and other bits (pids and whatnot) were scattered around the filesystem. Now that I'm using "layout: local", mailman really is trying to keep everything under that main directory, and now everything's breaking. The hyperkitty search indexer is saying it has no permissions to write into that directory, postfix won't deliver mail, saying the mailbox is unavailable, and in the web UI postorius shows no configured list domains (though hyperkitty still displays the archives correctly). So obviously I've got quite a big problem with permissions, but I don't know how to resolve it. My webserver is nginx, running as www-data. I'm starting mailman in a systemd script, with User and Group set to my user -- though maybe that should be set to root? I guess postfix runs as root, I'm not sure, but obviously it's not able to read the files in var/data/*, which appear all correct to me. What's the recommended solution here? I'd still like to keep this whole directory under my home directory, if possible... Thanks, Eric

1 0