I saw in the docs:
> We have it! We just don’t have proper documentation here yet.
Could you please be more specific - can I switch Mailman 3 installation to
#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
I want to install mailman 3 in a centos 7 virtual machine. I'm following
these steps and I cannot make it work:
1. `cd ~`
2. `git clone https://gitlab.com/mailman/mailman.git`
3. `cd mailman`
4. `virtualenv -p python3 venv`
5. `source venv/bin/activate`
6. `python setup.py develop`
7. I am pretty sure this setup command will place a configuration file into
`~/mailman/var/etc/mailman.cfg`. Edit this file.
8. `mailman info` can confirm which configuration file is in use
9. `mailman start` will start up Mailman 3 Core. This is what the parent
background process command looks like in `ps -ef`:
I also tried the steps on the website
but it doesn't work either
What do you suggest?
This is what I get from console:
[root@localhost ~]# cd dev/
[root@localhost dev]# cd mailman/
[root@localhost mailman]# source venv3/bin/activate
(venv3) [root@localhost mailman]# cd mailman/
(venv3) [root@localhost mailman]# ls
conf.py COPYING data README.rst src
contrib coverage.ini MANIFEST.in setup.cfg template.py
copybump.py cron port_me setup.py tox.ini
(venv3) [root@localhost mailman]# cd ..
(venv3) [root@localhost mailman]# mailman start
Starting Mailman's master runner
/root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': [Errno
2] No such file or directory
(venv3) [root@localhost mailman]#
Atentamente / Best Regards
Ing. Rafael Mora
The LMTP runner on my Mailman 3 install (3.1.0b4) has started silently
crashing. The parent process and all of the other runners stay up. Nothing
interesting seems to be written to the logs. I've been finding out about it
when exim4 (running on the same server) starts sending out "retry timeout
exceeded" bounce emails to list participants:
From: Mail Delivery System [mailto:Mailer-Daemon@lists.mysite.org]
> Sent: Monday, July 31, 2017 12:39 PM
> To: some_participant(a)mysite.org
> Subject: Mail delivery failed: returning message to sender
> This message was created automatically by mail delivery software.
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> retry timeout exceeded
> Action: failed
> Final-Recipient: rfc822;listname(a)lists.mysite.org
> Status: 5.0.0
After hearing about the bounces from participants, I then SSH to the lists
server and attempt to `telnet localhost 8024` but get no response. The LMTP
runner is not listed in `ps -ef`. After restarting all of mailman (`mailman
stop; mailman start`) I get the `220` response from LMTP on port 8024. I
see the LMTP runner in `ps -ef`.
Does anyone have any ideas on how I could start debugging this?
So I am looking to install the latest mailman 3, however I can find no
complete guide as to how to install it. I have found some pages for
This however gives me no instructions on how to install mailman3.x, can
anyone point me in the righ direction please.
Advanced Systems Engineer
Mailman 3 Status Update Please
I have been following the progress and difficulties with great interest
as many struggle to implement the new version of the great Mailman 3
list-server software. Last year about this time I posed some questions
regarding the current development status and recognize that many
additional problems seem to get in the way of actually working on long
term big picture issues.
From my perspective of being an senior (ie overaged) person desirous of
implementing fully-featured, capable, scalable, reliable, secure
applications such as Mailman, I am convinced that I am thoroughly over
From my limited perspective, it would seem to me that a 'nice to have'
system would incorporate the following.
1. An open container standard configurable system install, compatible
with different web & mail servers, DB utilities, etc;
2. Python 3 version Django utilities for archiving and mail list name
3. A design/plan from an inside expert perspective stating costs, time
and resources to implement the plan, incorporating crowdfunding to
pay for project.
4. As a backup incentive to the crowdfunding plan might be the offer of
an expert to set up a system for each significant amount donated,
say US$1,000, such as might be accomplished by an SSL session on the
target computer/server after the user has specified all necessary
detail as required in a template.
I am sure that the program author and other major contributors could
greatly enhance this list.
In summary, I guess what I am requesting is an overview forecast by half
year period and out for the next two years?
Please share the big picture?
Thank you in advance and best regards.
I've managed, to setup MM3.1 using the docker images from
http://github.com/maxking/docker-mailman. I would like to start customizing
the templates MM3.1 uses for the footer and confirmation emails. Is there
any mailman site admin or list admin documentation on how to customize
email templates in MM3.1? I've found this template doc at
I'm not clear how this works.. and it appears postorius doesn't have
template support yet? I am new to python and django..
I've just installed Mailman 3.1 on RHEL7 (Docker-Mailman3) and to get the right CSS layout I installed Apache on the Mailman server outside Docker, as advised by Abhilash Raj and Alexander Klotz.
My Mailman server is on a secured network and the https connection from Internet will be handled by proxy servers, so I will be using http (port 80) between proxy-servers and Mailman server.
But when I sign in (currently via an SSH tunnel to the Mailman server from my workstation) I get "Internal error: [client ::1:41912] AH01102: error reading status line from remote server 172.19.199.3:8000, referer: http://localhost/accounts/login/?next=%2Fpostorius%2Flists%2F"
If I type a wrong password, I am just warned about that, so the problem appears when log in is accepted.
I expect that it is because I connect to localhost:80 through SSH tunnel. What do I miss in my Apache configuration on the Mailman server to avoid this problem?
CustomLog /var/log/httpd/access_log combined
Alias /static /opt/mailman/web/static
Alias /favicon.ico /opt/mailman/web/static/hyperkitty/img/favicon.ico
ProxyPassMatch ^/static/.* !
ProxyPass / http://172.19.199.3:8000/
ProxyPassReverse / http://172.19.199.3:8000/
Allow from all
Require all granted
Allow from all
Require all granted
# ssl config here ...