- Mailman-users - lists.mailman3.org

About mailing list configuration problem
by liutianhua68＠163.com April 20, 2022

April 20, 2022

Hello: I installed mailman3 through docker, and I created a mailing list for testing, which can subscribe, unsubscribe, receive emails, and send emails normally. Now there are two problems that have not been resolved. I would like to ask: 1. When a user subscribes, how to configure it like "lists.mailman3.org" to send a link to confirm the subscription instead of just replying to the confirmation email. 2. I used the mailling list I created to test the sending and receiving of emails, but I didn't see any historical messages in "Archives",Where is the configuration incorrect? And the url of my mailing list is "https://list.example.org/hyperkitty/list/" instead of "https://lists.mailman3.org/archives/list/", is this a problem? Also ask about the configuration, where to find the relevant documentation. thank you very much. liutianhua68(a)163.com

3 2

Prometheus mailman_exporter
by Ruth Ivimey-Cook April 19, 2022

April 19, 2022

Folks, I have recently been playing with Prometheus metrics, and having now coded a mailman3 Prometheus exporter in python I thought I'd mention here that it exists. It's not fancy and there is more to do. It works using the rest api. Source available at https://github.com/rivimey/mailman3_exporter Metrics exposed: 'mailman_up' (does the API /system/versions return http 200) and 'mailman_queues' (queue lengths for each queue, plus 'status' for the http status code of that query) Suggestions for other metrics would be interesting if accompanied with info on how to extract it. I'm currently contemplating including the number of 'to be moderated' messages. It would be possible to include the number of lists or domains but not sure it's useful enough to be worth the cost of fetching it. It is passed the api auth data separately. It would be better to read it from mm config: is there existing code I can call? Regards, Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

2 1

How to create my first mailing list
by liutianhua68＠163.com April 19, 2022

April 19, 2022

Hello: I have installed mailman3 with docker, configured "MAILMAN_ADMIN" in docker-compose.yaml, but after logging into web with this user, there is nowhere to create mailing list. How should I create a super admin account now or where to create the first mailing list, is there any reference documentation, please help, thanks. liutianhua68(a)163.com

2 1

MAILMAN_ARCHIVER_KEY - 401 error
by Torsten R. April 14, 2022

April 14, 2022

Hi together, I just updated one of my servers to Debian 11 and that also introduced mailman3 to the system as I was running mailman 2.1 for years before on that server. It took me a while to configure everything but I am convinced that I now have everything done properly. I am able to access the web interface of mailman3 (postorius) and also the archive (hyperkitty). I configured exim to deal with messages send to the lists. But when I try to send a message (as a member of a list) to a list I always get a 401 in mailman.log and the message that I should check if I provided MAILMAN_ARCHIVER_KEY and if it is correct. So far, I can say that the key is the same in mailman-web.py (with single quotes) and mailman-hyperkitty.cfg (without quotes). in mailman-web.py I have: MAILMAN_ARCHIVER_KEY = 'somesecretkeywithlotsofcharacters' and in mailman-hyperkitty I have this: api_key: somesecretkeywithlotsofcharacters I have some messages in $var_dir/archives/hyperkitty/spool but mailman qfile <messagefile> doesn't show anything that would catch my eye. So, maybe I need another pair of eyes that could take a look at my configs or someone that is turning me in the right direction and might give some hints where to look and what to check. Thanks, Torsten

2 8

Lessons learned and a couple little gotcha for newbies
by William Oliver April 13, 2022

April 13, 2022

I just finished, with great help from Mark Sapiro on the list, a new installation of mailman3. I used the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… and https://docs.mailman3.org/en/latest/install/virtualenv.html There were a couple of gotchas that I didn't see well documented. 1) I got the error django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- packages/mistune/scanner.py) when I ran 'mailman-web migrate' The fix was trivial: I just added the lines: from mistune.util import escape_html from mistune.util import escape_url to /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py It's not hard to search for those definitions, but if someone doesn't know a smattering of python, it might not be obvious. 2) Similarly, migrate (using postgres) also gave the error: File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/backends/postgresql/utils.py", line 6, in utc_tzinfo_factory raise AssertionError("database connection isn't set to UTC") I was able to find a discusson of this one at https://stackoverflow.com/questions/68024060/assertionerror-database-connec… which had me downgrade to an older version of psycopg2-binary: pip install psycopg2-binary==2.8.6 There might be a different fix, but this worked. 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the error: ModuleNotFoundError: No module named 'settings' This was also trivially fixed by adding the path: export PYTHONPATH=$PYTHONPATH:/etc/mailman3 in /opt/mailman/.bashrc 4) Sometimes when I rebooted the machine, when I ran 'systemctl start mailman3' I'd get the error that mailman wouldn't start because the lock was stll there. I never could figure out where the lock was, so I worked around it by replacing ExecStart=/opt/mailman/venv/bin/mailman start with ExecStart=/opt/mailman/venv/bin/mailman start --force in /etc/systemd/system/mailman3.service I'm sure there's something bad about doing that, but it works for me, so far. 5) I had a problem with mail to outside people not being delivered while mail to the local host was delivered. It turned out that this was because in my mailman.cfg I had "smtp_host:my.listserver.tld when it should have been localhost. The error was "relay access denied." To fix this, I had to add my.listserver.tld to "mynetworks" in /etc/postfix/main.cf, ie change: mynetworks = 127.0.0.0/8 10.0.0.0/24 to mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address However, Mark Sapiro (a God) told me this was because I had changed a line in the [mta] section of mailman.cfg. I had changed smtp_host: localhost to smtp_host: mydomain.tld Here's the thing. The reason I did this was because the instructions at https://docs.mailman3.org/en/latest/config-core.html give this as their model: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com <---- not localhost smtp_port: 25 The instructions are good, but there are a few places where one size does not fit all, I guess. 6) A second error in delivery to outside addresses resulted in an "Access denied" error. A search on the internet revealed that this had to do with (for me) smtpd_recipient_restrictions in postfix. See, for instance: https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… Changing this fixed things. I'm not sure, but I think this shows up mostly with installations that include dovecot. 7) If you are using virtual domains in postfix, you need to use the "unusual postfix configuration" in https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap 8) You need to manually set the local virtual host for mailman3. Somehow, I got the impression from the installation instructions that this was done automagically to the default x.mydomain.tld if your domain is mydomain.tld. It doesn't. 9) Follow the instructions verbatim, and follow them in the order provided. I installed postfix and nginx out of order, and it did OK, but once you get into the python virtual environment, it is easy to miss something if you don't do it in order. 10) Jot down lots of notes. This is one of the more complicated installations I've done, mostly because it involved configuring a zillion packages to talk to each other: Postfix, nginx, postorius, hyperkitty, django, and others (I'd never heard of "whoosh" or "sass" for instance). All of these can be unforgiving with configuration errors. The default installation instructions assumed a number of packages I'd never used. I'm an apache/dovecot/mysql kind of person, and I had to switch to nginx/postgres to use the instructions as the written defaults. I'm sure I could have used apache and mysql, but it would mean trying to figure out what didn't work without following the installations verbatim. I'd never even heard of postorius, hyperkitty, or django. So, it was easy to get confused a bit. Taking notes of changes I made was important in being able to back out of disastrous choices. Plus, once I'd installed it on one machine, I sat down and installed it on another machine, and it was very useful to have written down how I fixed an issue when it came up again -- and I didn't remember exactly what I had done. 11) Make multiple sequential backups of configuration files. I went down a couple of paths I shouldn't have gone down. For instance, with the vmap issue, I got it in my head that it was a postfix configuration issue, not a mailman issue. So I kept changing things in postfix. Once I was told that it was in *mailman* I had to set the virtual host, I needed to back out of about 8 tweaks I'd made to main.cf in /etc/postfix. If I hadn't been making main.cf.backup.01, main.cf.backup.02, etc. I would have had to spend another few hours trying to remember what inappropriate changes I had made. This is particularly true for me because I am not a great typist, and when I try to retype something to back out, there's a reasonable chance I'll mistype something and it still won't work. With these backups, I don't have both manually back out of things *and* proof my typing again and again. It's a lot easier to delete backups once things are working than to try to remember what you did late at night after a couple of bourbons. 12) Choose one set of installation instructions and follow it. Don't try to mix instructions from different tutorials unless you really know what you are doing. I didn't. For instance, there's a different set of mailman3 installation instructions at: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 It does things a little differently. It's useful to look at that when you are debugging why something's not working, but you can get into some trouble trying to do both installations at the same time -- which I found myself doing when something wasn't working. It didn't help. billo

3 6

Issue with send mail to my domain in mailman3
by Paul Ssekamatte April 12, 2022

April 12, 2022

I get this error in mail.log when I try to send mail to my domain Recipient address rejected: SMTP AUTH is required for users under this sender domain (in reply to RCPT TO command)). My setup is such that the server hosting the mailman3 (lists@tld) lists is different from the mail server (mail@tld) Please advise.

2 3

How to use the "recipient_delimiter" postfix parameter with Mailman3?
by Pierre Malard April 12, 2022

April 12, 2022

Hi, We are using the « recipient_delimiter » parameter with our Postfix server as « _ ». Visibly, Mailman have it’s own mail configuration because it doesn’t work know. Is it a way to conserv this Postfix functionality? Thanks -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « La façon de donner vaut mieux que ce que l'on donne » Pierre Corneille (1606-1684) - Le menteur |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 3

french translation
by Yvan ♞ April 11, 2022

April 11, 2022

Hello is there any french translation for mailman 3 ? to make it more user friendly to users. Sincerely

2 1

Re: Mailman3 reinstall fail, need some help
by Yvan ♞ April 11, 2022

April 11, 2022

Yes it's debian and I have root access but it's a more "user friendly" server release. I tryed this but it block https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md https://yunohost.org/en/administrate/whatisyunohost Sincerely Yvan Le 12/03/2022 à 15:28, Eggert Ehmke a écrit : > Hello Yvan, > > I would suggest to install mailman3 following this guide: > https://docs.mailman3.org/en/latest/install/virtualenv.html > > but at first check, which operating system is on your yunohost? Is it Debian/ > Ubuntu? In this case the guide is fine, else there will be some adaptions. > > Tell me some details of your system, and if you have root access and can > install software packages. > > Regards > Eggert > > Am Samstag, 12. März 2022, 15:16:11 CET schrieb Yvan ♞: >> Hello, just made a try to install mailman 3 on yunohost unsuccessfully >> Sad... >> If some body can help me... >> Thanks >> https://paste.yunohost.org/raw/hujesebita >> >> Le 07/02/2022 à 15:57, Stephen J. Turnbull a écrit : >> >>> Yvan ♞ writes: >>> >>> >>> >>> > Just to know if I have a chance, do I have to unistall mailman before >>> > installing mailman 3 ? >>> >>> >>> >>> No. In fact, you can run both at the same time. Not for the same >>> list, obviously. And it requires a fair amount of planning and careful >>> attention to your web and MTA configurations. As far as I know there >>> are no naming conflicts in the default installations, Mailman 2 >>> installs into directory trees under directories named "mailman", while >>> Mailman 3 installs under "mailman3". >> _______________________________________________ >> Mailman-users mailing list --mailman-users(a)mailman3.org >> To unsubscribe send an email tomailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >

4 9

template head/footer questions.
by bob B April 11, 2022

April 11, 2022

I migrated from mailman 2 to mailman3 and had head/footer questions. In the mailman 3 GUI see the templates section, so where do those files get edited/stored? I added a footer to a list via the GUI, but I do not see it in: /var/templates/lists/[listNAME]/en I see some directories corresponding to list names in /var/templates/lists/ But I do not have a directory for all my lists and for the footer one I just added. Bottom line, I assume I should not edit or create any files in /var/templates/lists/ and just use the GUI? is this directory leftover from migrating from mailman 2 to 3? I have a list admin who has made some head and footer files and wants me to put them in /var/templates/lists/[listNAME]/en/.... but I think that may not be the best option.

2 1