Post installation issues (recipients refused) with Exim4 in a virtual host environment
by Kyriakos Terzopoulos
Hi,
I have set up (I believe successfully) and configured the following in a
Virtualhost environment (with HestiaCP):
- A record for lists.mydomain.com
- Venv
- Mailman core
- Mailman web (run migrate, collectstatic, compress, compilemessages)
Postorius
- gunicorn, hyperkitty
- Nginx
- SMTP exim4 conf
I can see Posrorius and I have logged in and created my first mailing list:
[image: Screenshot 2023-10-11 at 10.57.31 AM.png]
My issue is that even though I have subscribed to my list as you can see
above, I am not receiving the confirmation email. I get a "recipients
refused" error. The smtp log for mailman is as follows:
Oct 11 10:41:20 2023 (1533666)
<169701007904.1534165.14569329382406660776@localhost> recipients refused: {'
kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for
<testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable
address\nSender verify failed')}
Oct 11 10:41:20 2023 (1533666)
<169701007904.1534165.14569329382406660776@localhost> smtp to
testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 seconds
Oct 11 10:41:20 2023 (1533666)
<169701007904.1534165.14569329382406660776@localhost> post to
testlist(a)myproject.eu from
testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu,
1667 bytes, 1 failures
Oct 11 10:41:20 2023 (1533666)
<169701007904.1534165.14569329382406660776@localhost> delivery to
kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed
for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable
address\nSender verify failed'
I have used the configuration for exim that is here
<https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>
and
I have also tested with the alternative approach that is documented in
there.
------
Debug info follows:
First, here is my installation directory:
[image: image.png]
The following are the services that are running successfully (albeit with
some warnings):
------
*Mailman:*
● mailman3.service - GNU Mailing List Manager
Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor
preset: enabled)
Active: active (running) since Thu 2023-10-05 12:32:08 EEST; 28min ago
Process: 1563357 ExecStart=/opt/mailman/venv/bin/mailman start
(code=exited, status=0/SUCCESS)
Main PID: 1563364 (python3)
Tasks: 18 (limit: 9255)
Memory: 929.7M
CPU: 22.818s
CGroup: /system.slice/mailman3.service
├─1563364 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg
├─1563370 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=archive:0:1
├─1563371 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=bounces:0:1
├─1563372 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=command:0:1
├─1563373 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1
├─1563374 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1
├─1563375 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1
├─1563376 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1
├─1563377 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=pipeline:0:1
├─1563378 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1
├─1563379 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1
├─1563380 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1
├─1563381 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=virgin:0:1
├─1563382 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg
--runner=digest:0:1
├─1563420 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1
└─1563421 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1
Oct 05 12:32:07 hestia. mydomain.eu systemd[1]: Starting GNU Mailing List
Manager...
Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Starting Mailman's
master runner
Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Generating MTA alias
maps
Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: *mailman3.service: Can't
open PID file /opt/mailman/venv/master.pid (yet?) after start: Ope*>
Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: Started GNU Mailing List
Manager.
*Note the above warning for the master.pid file. However the file exists
and is writeable*
------
*Mailman web service*
● mailmanweb.service - GNU Mailman Web UI
Loaded: loaded (/etc/systemd/system/mailmanweb.service; disabled;
vendor preset: enabled)
Active: active (running) since Thu 2023-10-05 12:51:46 EEST; 9min ago
Main PID: 1578503 (gunicorn)
Tasks: 2 (limit: 9255)
Memory: 67.2M
CPU: 753ms
CGroup: /system.slice/mailmanweb.service
├─1578503 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf
mailman_web.wsgi:application
└─1578505 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf
mailman_web.wsgi:application
Oct 05 12:51:46 hestia.mydomain.eu systemd[1]: Started GNU Mailman Web UI.
Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!!
Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! *WARNING:
configuration file should have a valid Python extension*.
Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!!
*Another warning above, however the service is starting normally.*
------
*Django Qcluster*
● qcluster.service - HyperKitty async tasks runner
Loaded: loaded (/etc/systemd/system/qcluster.service; disabled; vendor
preset: enabled)
Active: active (running) since Thu 2023-10-05 12:51:40 EEST; 10min ago
Main PID: 1578463 (mailman-web)
Tasks: 8 (limit: 9255)
Memory: 101.2M
CPU: 30.915s
CGroup: /system.slice/qcluster.service
├─1578463 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578465 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578466 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578467 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578468 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578469 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
├─1578470 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
└─1578471 /opt/mailman/venv/bin/python3
/opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3
--settings settings
Oct 05 12:51:40 hestia. mydomain.eu systemd[1]: Started HyperKitty async
tasks runner.
Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578463]: 09:51:40 [Q]
INFO Q Cluster washington-solar-muppet-alanine starting.
Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578466]: 09:51:40 [Q]
INFO Process-1:1 ready for work at 1578466
Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578467]: 09:51:40 [Q]
INFO Process-1:2 ready for work at 1578467
Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578468]: 09:51:40 [Q]
INFO Process-1:3 ready for work at 1578468
Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578469]: 09:51:40 [Q]
INFO Process-1:4 ready for work at 1578469
Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578470]: 09:51:41 [Q]
INFO Process-1:5 monitoring at 1578470
Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q]
INFO Process-1 guarding cluster washington-solar-muppet-alanine
Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q]
INFO Q Cluster washington-solar-muppet-alanine running.
Oct 05 12:51:41 hestia.mydomain.eu mailman-web[1578471]: 09:51:41 [Q] INFO
Process-1:6 pushing tasks at 1578471
------
Nginx (hestia CP virtual hosts)
server {
listen 1.2.3.4:80;
server_name lists.mydomain <http://lists.mydomain.com>.eu;
location /static/ {
alias /opt/mailman/venv/web/static/;
}
location / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $remote_addr;
}
}
------
Happy to share my other mailman or EXIM4 configuration files if needed.
Thanks in advance.
Kyriakos
___________________________________________
Mailman's content filtering has removed the
following MIME parts from this message.
Content-Type: image/png
Name: image.png
Content-Type: image/png
Name: =?UTF-8?B?U2NyZWVuc2hvdCAyMDIzLTEwLTExIGF0IDEwLjU3LjMx4oCvQU0ucG5n?=
Replaced multipart/alternative part with first alternative.
2 years, 5 months
Difficulties setting up MM3 with Postfix MTA in Docker Environment: Invalid EHLO domain name & Authentification as lists.local
by Niklas Frühauf
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" "-"
7 years, 4 months
Re: Upgrade-path from Ubuntu18LTS to recent mailman release
by Stefan Bauer
Thank you all for your time. I managed to do a fresh installation. The MM
documentation is very good.
As i only use sqlite, i will give it a try to just copy the database files.
Stefan
Am Do., 5. Mai 2022 um 11:11 Uhr schrieb Stephen J. Turnbull <
stephenjturnbull(a)gmail.com>:
> Stefan Bauer writes:
>
> > thanks alot. That looks promising. Can we just copy the current
> > mailman3-database and take the configurations or is there a specific
> > migration path we have to follow?
>
> Much of the documentation on mailman.readthedocs.io discusses
> migrations and upgrades. You should read those for general hints.
>
> The distro Mailman to venv Mailman case is more discussed here on the
> mailing list than in those documents. I don't have pointers to those
> threads or the time to look offhand, maybe over the next few weeks as
> I work on our GSoC project. If you do find any, and would post them
> here, I'll make sure they get into the docs.
>
> The main thing is to backup Mailman configs (probably in /etc/mailman
> or /etc/mailman3) and the backend database (core, Postorius, possibly
> HyperKitty depending on configuration, and the django-mailman auth
> stuff) before trying to migrate. (For the backend database I would
> just dump the RDBMS unless non-Mailman content is really huge.) The
> nature of the virtualenv install is such that it *will not* overwrite
> any of the distro files at all (as long as you put it in /usr/local or
> /opt). However, you want to preserve the configs and database and
> reuse them, so those *must* be backed up.
>
> > We are currently running 3.1.1-9 (Ubuntu 18).
>
> Ubuntu 18 is probably old enough that you need to be careful about
> MySQL and its derivatives. The specific problems are (1) you need to
> specify the right UTF-8 variant for the coding system, and (2) more
> recent versions of Mailman tend to make certain records overflow.
>
> If you're using PostgreSQL these caveats *do not* apply. If you're
> using sqlite3 (I doubt it, but just for completeness) you should
> change to PostgreSQL or MySQL. If you're using something else (same
> caveat), I can't really say. Probably somebody out there is using
> Oracle or whatever, but we don't know about that. :-)
>
> Steve
>
>
3 years, 10 months
Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header
by Torge Riedel
Am 18.01.20 um 19:38 schrieb Mark Sapiro:
> On 1/18/20 6:58 AM, Torge Riedel wrote:
>> Am 16.01.20 um 21:43 schrieb Mark Sapiro:
>>> This won't work for posts from members because the header checks are
>>> done between member moderation checks and non-member moderation checks,
>>> but if you create a Header Filter for header 'x-spam' and pattern 'yes'
>>> with action hold, a message from a non-member which has an X-Spam: Yes
>>> header should be held for that reason.
>>>
>>>
>> Hi Mark,
>>
>> thank you for your answer. Just to understand that right: In case a
>> posting with an "X-Spam: Yes" header comes from a member, it will not be
>> held? It will be directly forwarded to the list?
> No. I apologize for being unclear.
>
> A post from a member will first be handled according to that member's
> moderation action which may be the list's default action for posts from
> members or a specific action for that member.
>
> If that moderation action is reject, discard or hold, the post will be
> rejected, discarded or held as a moderated member post regardless of any
> header filters.
>
> If the action is accept, the post will be accepted without any further
> checks including the header checks.
>
> If the action is defer (default processing) the message will be held for
> matching the X-Spam: Yes header.
>
> What I meant was if the member's (or default) action was hold, the post
> would be held, but the reason would be moderated member, not header match.
>
> The bottom line here is the moderation action of accept should only be
> used in cases of a highly trusted member (such as a list owner) because
> it bypasses other checks, but the address is still subject to spoofing.
> In the normal case where a moderation hold is not desired, use the defer
> (default processing) action.
>
Hi Mark,
thanks for clarification. I will add a header filter.
One final question: When adding a new header filter I can select between different actions. And there is one named "Default Anti-Spam action" (roughly translated from German). I cannot find anything else about this somewhere else in the settings (Postorius). So what it is the "Default Anti-Spam action"?
Best regards
Torge
6 years, 1 month
Re: problem configuring mailman3 on debian bullseye
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia
Hi,
I created a template but after some tests I deleted it.
Now I created only a standard list without modifying any templates.
So they are the standard templates coming with the distribution. I did
not change also the language
Roberto Burceni
Servizio informatico sezionale
Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00
E-mail:
servizioinformatico(a)uicibrescia.it
Sito web:https://www.uicibrescia.it
Il 15/03/23 16:30, Odhiambo Washington ha scritto:
>
>
> On Wed, Mar 15, 2023 at 6:21 PM Servizio Informatico U.I.C.I. Sezione
> territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote:
>
> Hello all,
>
> I'm a blind server administrator living in Italy. I use mailman since
> 2010 and I was very happy for this list manager.
>
> When was released the version 3 I started to have many problems to
> configure it.
>
> In this days I installed a new server for my association and I
> have this
> problem that I don't know to solve.
>
> The server is a debian bullseye.
>
> I installed mailman3-full from the standard packege.
>
> I'm using nginx as web server.
>
> I configured mailman3 and mailman3-web wit https support.
>
> All is working fine, but if I attempt to subscribe someone it does
> not
> work.
>
> I send a subscription e-mail to the address list and I receive
> correctly
> the request to confirm subscription. When I reply to the request
> mailman
> log gives this error:
>
> requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost',
> port=443): Max retries exceeded with url:
> /postorius/api/templates/list/listname.domain/list:user:notice:welcome
>
> (Caused by SSLError(SSLCertVerificationError("hostname 'localhost'
> doesn't match either of 'example.com <http://example.com>',
> 'www.example.com <http://www.example.com>'")))
>
> The strange thing is that I configured a domain list.example.com
> <http://list.example.com> and in
> the configuration files I put this domain.
>
> Mailman3-web works fine I can create lists and make settings.
>
> Have you an idea about this issue?
>
>
> Assuming that you created this template - list:user:notice:welcome -
> what are its contents?
>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
2 years, 11 months
MHonArc archiver setup/config?
by Stephen J. Turnbull
Bryan Fields writes:
> I've had a request to setup this for a mm3 list. It looks like it's supported
> from the config files,
From the comments in the implementation files, I would say that no
consideration has been given to private archives. I don't know how
MHonArc handles that, so if it's a concern I can only warn you to be
careful.
> but I'm at a loss for exactly how to go about this.
> Has anyone setup this with mm3 and can provide an overview?
I haven't set it up. However, what I would do is
1. Copy .../mailman/config/mhonarc.cfg to /etc/mailman3 (or wherever
you keep mailman.cfg).
2. Edit base_url and command in /etc/mailman3/mhonarc.cfg.
base_url may already be appropriate for your system, but the
"/path/to/archive" part of command will need to be adjusted.
$hostname, $listname, and $fqdn_listname are variables supplied by
Mailman at runtime. I don't know enough about MHonArc to say if
the usage of $listname (just the local part of the posting
address) and $fqdn_listname (posting address including domain) is
appropriate. I would think you'd want to use the same variable in
both places, so be careful.
3. Create any directories in "/path/to/archive" that MHonArc won't,
and make sure they have appropriate ownership and search ("x")
permissions all the way down.
4. Check that your webserver is configured to serve MHonArc at the
location specified in base_url.
5. Add the stanza
[archiver.mhonarc]
enable: yes
configuration: /etc/mailman3/mhonarc.cfg
to /etc/mailman3/mailman.cfg
6. (Recommended) Mailman is perfectly happy to supply several
archivers at the same time so add
[archiver.prototype]
enable: yes
to mailman.cfg.
This drops all the posts into a maildir somewhere under $var_dir
as a backup in case the MHonArc archiving doesn't work, and
nothing else -- it's not a usable archive for browsing. I guess
there's probably a way to import them back into MHonArc, but if
not presumably you can script it usng some variant of the command
in mhonarc.cfg.
Once the MHonArc configuration is doing the right thing you can
disable it and delete the maildir contents. (Don't just "rm -rf
$var_dir/archive", though -- Mailman uses that to queue messages
being archived. I think archiver.prototype uses
$var_dir/archive/prototype as its maildir.)
7. Restart Mailman.
I don't think you need to do anything for Postorius, it will fetch the
base_url from Mailman to populate the archive links. And that should
do it on the Mailman side (except for the caveat about private
archives).
Steve
1 year, 1 month
Re: Archive Policy not reflecting in Hyperkitty
by Nathan Dixon
I'm not sure if it's also related, but within the mailman-web and
mailman-core docker containers, crontab -e only shows these entries:
# do daily/weekly/monthly maintenance
# min hour day month weekday command
*/15 * * * * run-parts /etc/periodic/15min
0 * * * * run-parts /etc/periodic/hourly
0 2 * * * run-parts /etc/periodic/daily
0 3 * * 6 run-parts /etc/periodic/weekly
0 5 1 * * run-parts /etc/periodic/monthly
And all of those folders are empty.
I'm not sure where the synchronisation task for Hyperkitty should actually
being run from?
Thank you
On Tue, 7 May 2019 at 10:20, Nathan Dixon <nathan.dixon(a)evadon.com> wrote:
> The change to the archiving policy aren't reflected in Hyperkitty after
> many days for all the lists.
>
> The only error that I am seeing in the /web/mailmanweb.log is:
> INFO 2019-05-02 14:16:55,062 38 hyperkitty.tasks AsyncTask task "<function
> unlock_and_call at 0x7f5d8851f048>" with args "(<function
> update_from_mailman at 0x7f5d88544a60>, 'task:status:%s:%s', '<list
> address>')" and kwargs "{}" finished with errors.
>
> I'm not sure if that could be related? (I have changed the actual list
> address to <list address> for security reasons)
>
> Thank you
>
> On Sat, 4 May 2019 at 16:24, Abhilash Raj <maxking(a)asynchronous.in> wrote:
>
>> On Fri, May 3, 2019, at 8:38 AM, Nathan Dixon wrote:
>> > So the issue I am seeing is that when I set a lists archive policy to
>> > prviate, it isn't reflecting that in Hyperkitty.
>> >
>> > I am running the docker installation of Mailman, postorius and
>> hyperkitty.
>> > So I go into the docker instance of mailman-core and run this:
>> >
>> > python3 manage.py shell from hyperkitty.models.mailinglist import
>> > MailingList MailingList.objects.all().values_list('name',
>> 'archive_policy')
>> >
>> > And all my lists are showing '2', regardless of how I set the mailing
>> list
>> > archive policy.
>> >
>> > This might be a duplicate of
>> >
>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…
>> >
>> > Am I missing something in my install? Or is this a bug?
>>
>> It can take upto an hour for this change to reflect in Hyperkitty. Did
>> you wait
>> for that long?
>>
>> This happens because Hyperkitty stores it's own data, and queries Mailman
>> Core periodically to fetch updates every hour. In future, we might be
>> able to
>> do this in more realtime fashion by using an event based pub/sub model.
>> But,
>> we are not there yet.
>>
>>
>> >
>> > Many thanks for your attention,
>> >
>> > --
>> >
>> > *Nathan Dixon* MEng
>> > Senior Software Architect
>> > m: +44 (0)7402 690311
>> >
>> > t: +44 (0)20 81231252
>> > e: nathan.dixon(a)evadon.com
>> > w: www.evadon.com
>> >
>> > This e-mail and any attachments are confidential and may be protected by
>> > legal, professional or other privilege. If you are not the intended
>> > recipient you should not store it, copy it, re-transmit it, use it or
>> > disclose its contents, but should return it to the sender immediately
>> and
>> > delete your copy from your system. The views expressed are those of the
>> > sender and not necessarily those of Evadon. Please note that whilst we
>> scan
>> > all e-mails for viruses we cannot guarantee that any e-mail is
>> virus-free.
>> > Please be advised that we expressly reserve the right to monitor email
>> > content for the purposes of ensuring compliance with legal requirements
>> and
>> > company policies and your sending to, or receiving from, us of any email
>> > constitutes your agreement to these terms.
>> >
>> >
>> > Evadon Dynamics Limited, registered in England No. 09494097. Registered
>> > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way,
>> Sheffield,
>> > S1 2BJ
>> > _______________________________________________
>> > Mailman-users mailing list -- mailman-users(a)mailman3.org
>> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>> >
>>
>> --
>> thanks,
>> Abhilash Raj (maxking)
>> _______________________________________________
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>
>
>
> --
>
> *Nathan Dixon* MEng
> Senior Software Architect
> m: +44 (0)7402 690311
>
> t: +44 (0)20 81231252
> e: nathan.dixon(a)evadon.com
> w: www.evadon.com
>
> This e-mail and any attachments are confidential and may be protected by
> legal, professional or other privilege. If you are not the intended
> recipient you should not store it, copy it, re-transmit it, use it or
> disclose its contents, but should return it to the sender immediately and
> delete your copy from your system. The views expressed are those of the
> sender and not necessarily those of Evadon. Please note that whilst we scan
> all e-mails for viruses we cannot guarantee that any e-mail is virus-free.
> Please be advised that we expressly reserve the right to monitor email
> content for the purposes of ensuring compliance with legal requirements and
> company policies and your sending to, or receiving from, us of any email
> constitutes your agreement to these terms.
>
>
> Evadon Dynamics Limited, registered in England No. 09494097. Registered
> Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield,
> S1 2BJ
>
--
*Nathan Dixon* MEng
Senior Software Architect
m: +44 (0)7402 690311
t: +44 (0)20 81231252
e: nathan.dixon(a)evadon.com
w: www.evadon.com
This e-mail and any attachments are confidential and may be protected by
legal, professional or other privilege. If you are not the intended
recipient you should not store it, copy it, re-transmit it, use it or
disclose its contents, but should return it to the sender immediately and
delete your copy from your system. The views expressed are those of the
sender and not necessarily those of Evadon. Please note that whilst we scan
all e-mails for viruses we cannot guarantee that any e-mail is virus-free.
Please be advised that we expressly reserve the right to monitor email
content for the purposes of ensuring compliance with legal requirements and
company policies and your sending to, or receiving from, us of any email
constitutes your agreement to these terms.
Evadon Dynamics Limited, registered in England No. 09494097. Registered
Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield,
S1 2BJ
6 years, 10 months
Re: Confirmation emails to Users has wrong domain name (example.com!)
by Abhilash Raj
On Wed, Sep 29, 2021, at 9:50 AM, Odhiambo Washington wrote:
> 1. Confirmation emails to Users has wrong domain name (example.com!)
> <https://docs.mailman3.org/en/latest/faq.html#id1>
> <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…>
>
> This happens when your reverse (SSL) proxy isn’t setting up the correct
> headers when proxying requests. Fix this by setting the right
> proxy_set_header directives:
>
> # For Nginx.
> location / {
> proxy_set_header X-Forwarded-Proto $scheme;
> proxy_set_header X-Forwarded-Host $host;
> proxy_pass http://localhost:8000/;
> }
>
> Appropriate headers for different web servers needs to be set if something
> other the
>
>
>
> How is this supposed to be mitigated in Apache when using WSGI?
It seems like Apache has this `ProxyPassReverse` thing, which should do the same job:
https://www.nginx.com/resources/wiki/start/topics/examples/likeapache/
I haven't tried it myself, but it might help!
>
> My config:
>
> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman
> user=mailman group=mailman
> WSGIPythonHome "/usr/local"
> WSGIProcessGroup hyperkitty
>
> <VirtualHost *:443>
> ServerName lists.doma.ain
> ServerAdmin odhiambo(a)gmail.com
>
> SSLEngine on
> SSLCipherSuite
> ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
> SSLCertificateFile
> "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem"
> SSLCertificateKeyFile
> "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem"
> SSLCertificateChainFile
> "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem"
>
> CustomLog /var/log/mm3-lists-access.log combined
> ErrorLog /var/log/mm3-lists-error.log
> LogLevel info
>
> Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico
> Alias /static /usr/local/mailman/static
>
>
> <Directory "/usr/local/mailman/static">
> Order Allow,Deny
> Require all granted
> Allow from all
> </Directory>
>
> WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py
> process-group=hyperkitty
> WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py
> process-group=hyperkitty
> WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py
> process-group=hyperkitty
> WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py
> process-group=hyperkitty
>
> <Directory "/usr/local/mailman/">
> <Files wsgi.py>
> Require all granted
> </Files>
> WSGIProcessGroup mailman-web
> </Directory>
>
> </VirtualHost>
>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft.", egrep -v '^$|^.*#' :-)
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
--
thanks,
Abhilash Raj (maxking)
4 years, 5 months
Weird response to postings after subscriptions and accounts
by Paul Arenson
I accidentally posted to a test account I had not actually used. Am reposting to my correct account. Sorry to the moderators.
In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself?
1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…
2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below"
3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org
4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER?
5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows:
"Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account.
To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com"
6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list!
To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by
sending a message to....... I then get a notice:
"Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member"
7) While if they send FROM THE interface it goes through.
8) What I am confused about.
Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post.
Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't.
Thanks.
PS I am running out of test accounts to use to test my own setup. Thanks.
paul!!!Subscribe to this list
still shows up at the bottom.
6 years, 5 months
MM3 not starting afte an upgrade
by Gelpi Andrea
Hi,
to day in a Debian system I upgraded some packages.
After the MM3 doesn't start anymore.
These are the packages I upgraded:
[UPGRADE] clamav:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] clamav-base:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] clamav-daemon:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] clamav-freshclam:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] clamdscan:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] gcc-10-base:amd64 10.1.0-4 -> 10.1.0-6
[UPGRADE] libc-l10n:amd64 2.30-8 -> 2.31-1
[UPGRADE] libclamav9:amd64 0.102.3+dfsg-1 -> 0.102.4+dfsg-1
[UPGRADE] libgcc-s1:amd64 10.1.0-4 -> 10.1.0-6
[UPGRADE] libnss3:amd64 2:3.42.1-1+deb10u2 -> 2:3.42.1-1+deb10u3
[UPGRADE] python3-django-hyperkitty:amd64 1.3.2-1 -> 1.3.2-1.1
[UPGRADE] python3-django-postorius:amd64 1.3.2-2 -> 1.3.2-2.1
[UPGRADE] qemu-guest-agent:amd64 1:3.1+dfsg-8+deb10u5 ->
1:3.1+dfsg-8+deb10u6
MM3 on start up says:
Jul 23 13:29:39 posta mailman3[2608]: Traceback (most recent call last):
Jul 23 13:29:39 posta mailman3[2608]: File "/usr/bin/mailman", line
11, in <module>
Jul 23 13:29:39 posta mailman3[2608]:
load_entry_point('mailman==3.2.1', 'console_scripts', 'mailman')()
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
Jul 23 13:29:39 posta mailman3[2608]: return self.main(*args, **kwargs)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/core.py", line 717, in main
Jul 23 13:29:39 posta mailman3[2608]: rv = self.invoke(ctx)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 69, in invoke
Jul 23 13:29:39 posta mailman3[2608]: return super().invoke(ctx)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
Jul 23 13:29:39 posta mailman3[2608]: return
_process_result(sub_ctx.command.invoke(sub_ctx))
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
Jul 23 13:29:39 posta mailman3[2608]: return
ctx.invoke(self.callback, **ctx.params)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
Jul 23 13:29:39 posta mailman3[2608]: return callback(*args, **kwargs)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func
Jul 23 13:29:39 posta mailman3[2608]: return
f(get_current_context(), *args, **kwargs)
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line
81, in start
Jul 23 13:29:39 posta mailman3[2608]: status, lock = master_state()
Jul 23 13:29:39 posta mailman3[2608]: File
"/usr/lib/python3/dist-packages/mailman/bin/master.py", line 104, in
master_state
Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0)
Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1]
Operation not permitted
There is a permission error, but on what?
Thanks for any help.
Regards
--
Gelpi ing. Andrea
--------------------------------------------------------------
It took the computing power of three C-64s to fly to the Moon.
It takes a 486 to run Windows 95. Something is wrong here.
--------------------------------------------------------------
5 years, 7 months