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
Hello all ,
I configured mailman3 following this contributer guide http://docs.mailman3.org/en/latest/devsetup.html but i'am still getting problem with the configuration of MySQL and postfix . Is this section is enough for MySQL configurations ?
url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8&use_unicode=1htmlI will appreciated if there are some documents to provide to cotinue the intergration of mailman3 .
Is there any tuto for postfix config ?
Thanks in advance
#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 have an active list for which I am trying to debug some deliverability
issues. When a user tells me that folks aren't getting their postings, I
check the archives first. In this case, I am getting a traceback saying
"thread matching query does not exist" when I try to go to the HyperKitty
page for the list. How can I debug this?
I am using Mailman 3 via the Docker containers documented here:
The container versions appear to be 0.1.
I currently run MM3.0 based on the old bundle installation. It seems
to work just fine although with a number of minor and major annoyances
that probably have been fixed now.
What is the rekommended way to upgrade to the newest version? (newest
_usable_ version, of course)? Is it docker-only with a migration from
the current solution to a docker based? If so, any ideas or pointers
on how to go about this?
* Docker-mail 0.1.1
* Mailman 3.1
* Postorius 1.1.1
* Hyperkitty 1.1.1
Settings -> Message Acceptance -> Acceptable aliases has a default of  resulting in "An error occured: [u'']" when saving. This fiend should be empty by default or at least accept the default when saving.
To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2:
On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2?
Henrik Rasmussen <her(a)adm.ku.dk<mailto:firstname.lastname@example.org>>
(With the hope that someone on the list can help me diagnose this problem, I’m posting a copy of the HyperKitty issue that I opened a few days ago: https://gitlab.com/mailman/hyperkitty/issues/151.)
Testing MailMan3, installed using the Docker containers 0.1.1 (with HyperKitty 1.1.1):
I have two lists with several discussions in each. The participants/comments stats for all discussions show multiple participants and multiple comments. (Note that the numbers are wrong, as discussed in #149.)
However, when I open a discussion, some of them only display the first message. Others display all messages, one displays only some, but not all, of the messages. In one case, the discussion showed the top two messages, but when a new message was added, it briefly showed and then it and the second message suddenly disappeared, leaving only the first message. In another case, the discussion only showed the top message, but then, for no apparent reason, the rest of the messages appeared.
I decided to start all over, removing the Docker containers and images, as well as the existing database... all gone.
With the newly created system and database, I created two new lists and three member-subscribers. I then created new threads and added several messages to the new threads. The messages came from all three of the members and were entered via email and HyperKitty. One thread was created from within HyperKitty.
All of the newly created threads are displaying the same behaviour: all of the subscribers received, via email, all of the messages, but only the first message of each thread is displayed in HyperKitty.
Suggestions for how to trace/diagnose the problem would be appreciated.
Finally we decided to install Mailman through the docker images provided by you (https://github.com/maxking/docker-mailman).
The deployment was very quick, and it works flawlessly, so we will keep this solution.
On the side I will try to deploy Mailman 3 through its independent modules, just for fun :)
From: "Abhilash Raj" <maxking(a)asynchronous.in>
To: "Ruben Ibanez" <ribanez(a)sciops.esa.int>
Cc: "mailman-users" <mailman-users(a)mailman3.org>
Sent: Sunday, August 20, 2017 11:25:34 PM
Subject: Re: [MM3-users] Which documentation to follow for installation
On Sun, 20 Aug 2017 20:50:39 +0200 (CEST)
Ruben Ibanez <ribanez(a)sciops.esa.int> wrote:
> Hi Abhilash,
> Thanks for your reply.
> The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that?
There are production environments running Mailman 3.1 right now if that is your
questions, see https://lists.mailman3.org. Although, I guess you already saw
that when subscribing to this list ;)
> Of course, I'm not asking for .rpm, .deb, etc... because I understand that's
> quite complex, but I tried it following all available guides, including the
> Contributor's Guide, and it seems impossible to get it running at the first
> time (or just to get it running) without getting crazy or fixing lots of
> unexpected errors during installation.
It would be helpful if you send in those errors here. It will help us debug
your problem and also improve the guide for the people using it in future.
One small problem about the configuration, off the top of my head, can cause
some problems in the "Mailman Suite Installation" Guide. I have that
on my todo to fix. But, apart from that everything else should work!
You would have to do some additional configuration for the web frontend to work
and for the mail servers to talk to Mailman and Frontend separately, both of
which is also mentioned in the documentation under "Configuring Mailman Core"
and "Configure Web Frontend".
Contributor's guide is not focused on deploying but just setting it up locally
to play with and modify the source itself.
> Have you tried to deploy Mailman 3.x strictly following the documentation?
I think people have used it in past to successfully deploy Mailman 3.x, but
without looking at the errors you are facing I don't have any clue as to why it
doesn't work for you!
> By the way, many thanks for your hard work!
> From: "Abhilash Raj" <maxking(a)asynchronous.in>
> To: ribanez(a)sciops.esa.int
> Cc: mailman-users(a)mailman3.org
> Sent: Saturday, August 19, 2017 8:55:20 AM
> Subject: Re: [MM3-users] Which documentation to follow for installation
> On Fri, 18 Aug 2017 09:40:37 -0000
> ribanez(a)sciops.esa.int wrote:
> > Hi everyone,
> > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to
> > look for documentation. I found two different sites:
> > https://mailman.readthedocs.io/en/latest/
> > http://docs.mailman3.org/en/latest/
> Both of the above are actually latest documentation,
> docs.mailman3.org should be the one to look for installations guidelines for
> the entire Mailman 3.x Suite,
> mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles
> the mail.
> This should be the best place to start, be sure to look at the Pre-Installation
> Guide if you are new to the Python ecosystem.
> > Do you know which one should be followed? Both at the same time? I find it
> > quite unclear... and this installation will be for an operational environment.
> > Also, there are some (official?...) docker images, but all images are for
> > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed.
> It is meant for Mailman 3.X series and is maintained by me. It currently
> includes the latest releases for all the Mailman's sub-projects, also Mailman
> Hope that helps!
This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.