What is the recommended way for updating installed the installed pkgs in
MM3 venv - to ensure that nothing breaks?
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
Hello Mark & all,
I have the venv installation on my Debian 11 system running. I followed your suggestion to
upgrade all packages. When upgrading hyperkitty by this command:
pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master
I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4.
All packages were upgraded fine. I applied the patch to
to change the mistune import line. When I run now
*CommandError: Conflicting migrations detected; multiple leaf nodes in the migration
graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).*
*To fix them run 'python manage.py makemigrations --merge'*
However, when I run the suggested command as:
$ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations --
No conflicts detected to merge.
Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my
production system. Would be nice to shed some light on this.
I have had an installation of mailman3 running for a year or so with
no problems. This was a manual installation. I ended up having to
change machines, so I decided to install using the debian 11 package.
It seems to have gone well except.... when I restart mailman3 service,
I get the following fail and error message:
oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3
Job for mailman3.service failed because the control process exited with
See "systemctl status mailman3.service" and "journalctl -xe" for
root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3
● mailman3.service - Mailman3 server
Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor
Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT;
Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg
start --force (code=exited, status=1/FAILURE)
Oct 11 15:09:43 emergenis.com mailman3: File
109, in start
Oct 11 15:09:43 emergenis.com mailman3:
Oct 11 15:09:43 emergenis.com mailman3: File
"/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in
Oct 11 15:09:43 emergenis.com mailman3: raise
Oct 11 15:09:43 emergenis.com mailman3: RuntimeError: command
failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1,
Operation not permitted
Oct 11 15:09:43 emergenis.com mailman3: command failure:
/usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation
Oct 11 15:09:45 emergenis.com systemd: mailman3.service: Control
process exited, code=exited, status=1/FAILURE
Oct 11 15:09:45 emergenis.com systemd: mailman3.service: Failed with
Oct 11 15:09:45 emergenis.com systemd: Failed to start Mailman3
Oct 11 15:09:45 emergenis.com systemd: mailman3.service: Consumed
9.193s CPU time.
Heres the ls for /var/lib/mailman3/data:
root@emergenis:/var/lib/mailman3/data# ls -l
-rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains
-rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp
The web interface comes up and seems to "work" but of course complains
that mailman3 isn't actually running.
I assume there's some posfix config I haven't done right, but I am
clueless as to what it is.
Thanks in advance for any pointers.
Where and how do I set the default setting of "Delivery status" to be "Enabled".
I'm not seeing any clues in mailman3-web/settings.py
At the moment, a new subscriber is neither "Enabled" or "Disabled".
Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists.
I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS:
ESX 6.7 (CPU: Intel(R) Xeon(R) Gold 6242)
SLES 15 SP3
Senior Systems Engineer
Anderson Computing & Information Services | ACIS
Mailman's content filtering has removed the
following MIME parts from this message.
Replaced multipart/alternative part with first alternative.
Sorry if this is an old topic. I'm in the process of migrating from 2.1 to
3.2. In my use case one of the advantages of Mailman 2.1 vs services like
Google Groups has been the ability to manage lists from the command line.
Things like using sync_members to update the list for a committee when the
membership of the committee is updated one a year, or like using
find_members and remove_members to remove a user from all mailing lists
when they leave the organization. Even the ability to script mailing list
So far I haven't found these commands in Mailman3. I hope there is a plan
to add these soon.
I've mainly setup mailman3 to replace our mailman 2.1 install using Ansible, a point I could do with some assistance on is setting the fqdn used programmatically. I've been doing alot of reading before creating this thread.
To create a domain I currently navigate to: https://serverfqdn.com/postorius/domains/ and click 'Add Domain'.
I believe this is setting the name of the Django site, please accept my apologies if I'm wrong and the SITE_ID=1 is then used, I am only planning to use one domain only. I'm using Postgres and when I check the contents of the Django_mailman3_maildomain table as below afterwards:
mailman3web=# TABLE django_mailman3_maildomain;
id | mail_domain | site_id
1 | mailman3-test2.guest.codethink.co.uk | 1
I have newly set up Mailman 3 on Ubuntu 20.04.
Sending and receiving mails between list members does work, but I am currently experiencing two issues:
1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty.
2) Archiving is activated within list settings, but there isn't any archive created.
I found this thread, where the first of these issues is also described:
Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me.
I am running Mailman 3.2.2 on Python 3 .8.10.
So I need to either upgrade Mailman Core or downgrade Python.
I already did
> apt-get upgrade
> apt-get update
Unfortunately this didn't upgrade Mailman Core's version.
Which steps do I have to undertake to upgrade Mailman Core?