August 2017 - Mailman-users - lists.mailman3.org

Deleting archives
by Henrik Rasmussen Sept. 14, 2017

Sept. 14, 2017

Docker-mailman 0.1: I have deleted some lists that I used for testing, but Hyperkitty seems to preserve the archives in the Available lists. Clicking on a list archive gets me to the archive of that list (with no posts because I haven't posted anything to the list). The URL is https://[WEBSITE]/hyperkitty/list/[LISTNAME](a)[LISTDOMAIN]/<https://[WEBSITE]/hyperkitty/list/%5bLISTNAME%5d(a)%5bLISTDOMAIN%5d/> (with a (a)), but when I click Manage subscription, the URI changes to https://[WEBSITE]/postorius/lists/[LISTNAME].[LIST<https://[WEBSITE]/postorius/lists/%5bLISTNAME%5d.%5bLIST>DOMAIN/ (with a dot instead of (a) which seems normal behavior) and I get a "Not Found The requested URL /postorius/lists/[LISTNAME]DOT[LISTDOMAIN]/ was not found on this server. " error. Of course I can't manage the subscription for a list I have deleted, but shouldn't the archive for a list be deleted along deleting the list. Henrik Rasmussen

1 1

Acceptable aliases defaults to []
by Henrik Rasmussen Aug. 30, 2017

Aug. 30, 2017

* Docker-mail 0.1.1 * Mailman 3.1 * Postorius 1.1.1 * Hyperkitty 1.1.1 Minor issues: 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: * http://www.list.org/mailman-admin/node23.html * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… 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:her@adm.ku.dk>> Copenhagen, Danmark

4 4

Moving mm2 mail archives to mm3
by Tom Browder Aug. 29, 2017

Aug. 29, 2017

Is there any way to move my old mm2 archives to mm3? Thanks. -Tom

4 4

Only first message displayed... sometimes
by Cameron Smith Aug. 28, 2017

Aug. 28, 2017

(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. Cameron Smith

1 0

Re: Which documentation to follow for installation
by Ruben Ibanez Aug. 28, 2017

Aug. 28, 2017

Hi Abhilash, 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 :) Many thanks! Cheers, R. 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[1]. I have that on my todo to fix. But, apart from that everything else should work! [1]: http://docs.mailman3.org/en/latest/prodsetup.html 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! > > Cheers, > RI > > > 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. > > http://docs.mailman3.org/en/latest/prodsetup.html > > 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 > 3.1. > > > Hope that helps! > > -- thanks, Abhilash Raj 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.

1 0

Bounce processing
by Mark Ziranski Aug. 26, 2017

Aug. 26, 2017

Hello, I read that mailman3 supports 'bounce processing' but I do not know how to configure it. I want to delete members automatically from a mailing list if the delivery has failed after a certain time of attempts because his mailbox has been removed or his mail server has been shutdown etc. There is also the case that an users mailbox is full (mailbox limit exceeded). Is possible to deal with this case too? Thanks.

3 4

HyperKitty misreporting statistics
by Cameron Smith Aug. 24, 2017

Aug. 24, 2017

Mailman 3, container images 0.1.1 HyperKitty 1.1.1 is showing incorrect numbers for the number of participants and the number of discussions. (All messages referred to below were submitted in August.) In one list, I have two threads. In one thread, I have three messages, each from a different email address, all submitted via email (as opposed to replying from within HyperKitty). The month page (clicking on “August”) of that list however, shows that thread as having one participant and no messages. Opening the list shows the same stats: “1 participants”, “0 comments”; all three messages are displayed. The other thread in the same list also shows one participant and no messages; it has two messages in it, one submitted via email, the other submitted via HyperKitty by a different subscriber. Opening the list shows both messages. The front page of that list shows zero participants and two discussions. A second list also has two threads with three email-submitted messages from different addresses. The monthly stats show one thread as having one participant and one message, the other as having one participant and zero messages. The front page shows one participant and one discussion. Cameron Smith

2 6

Users, members, accounts and subscribers
by Cameron Smith Aug. 24, 2017

Aug. 24, 2017

Oh my! In an attempt to introduce a friend to MailMan3, I had her subscribe to a couple of lists that I set up and we exchanged a few messages via the email interface. Then I introduced her to the web interface and we were both confused when she could not log-in/sign-in and was told that her email address was not recognized. It was only later that I realized that while she was a subscriber, she hadn’t yet signed up for an account. What is the point of “accounts"? Why can someone become a subscriber, but not have an account? I find the user/member/subscriber explanation at http://mailman.readthedocs.io/en/latest/src/mailman/docs/architecture.html to be very confusing. Cameron Smith

3 3

Setting default Mailman admin (Django superuser) password in Docker-mailman
by Henrik Rasmussen Aug. 23, 2017

Aug. 23, 2017

I just upgraded to Docker-mailman 0.1.1 and prior to that for some reason I had to somewhat start over, deleting my database. At both on my first and second attempt I wondered what the Django admin password would be. According to https://github.com/maxking/docker-mailman/ and https://github.com/maxking/docker-mailman/blob/master/web/README.md, setting MAILMAN_ADMIN_USER and MAILMAN_ADMIN_EMAIL in docker-compose.yaml will create a username for the admin user by default, but it doesn't mentioning setting a variable for the password. Creating a superuser using docker exec -it mailman-web python manage.py createsuperuser would normally request the password for the user indicated, but user "mailman" has already been registred. So to get to know the superuser password, I reset it using https://stackoverflow.com/questions/6358030/how-to-reset-django-admin-passw…. Why don't the installation guide on https://github.com/maxking/docker-mailman/ mention anything about how to set the password in the docker-compose.yaml file? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

2 1

Possible bug in Mailman 3.1 (Docker-mailman 0.1)
by Henrik Rasmussen Aug. 21, 2017

Aug. 21, 2017

Mailman 3.1, docker-mailman 0.1 While I was trying to automate distribution of the files in /opt/mailman/core/var/data/postfix_domains I found what I think must be a bug. Adding a new mail list (or deleting one) _does_ update the Postfix files /opt/mailman/core/var/data/ ,but adding a new mail domain does not. This is OK. But deleting a mail domain that have lists associated to it * does not issue a warning other than "Are you sure you want to permanently delete this domain?" which is not different from deleting mail domains without lists associated to it. * the associated lists disappears both from the web interface Lists view and from the output of the "docker exec -it mailman-core mailman lists" command * the files in /opt/mailman/core/var/data/ is not updated even the lists is being deleted. 1. Deleting a mail domain with associated lists should issue a warning that it has lists associated to it. 2. The files in /opt/mailman/core/var/data/ should be updated according to the deleted lists / domains. 3. Actually I think it should be impossible to accidentally delete a mail domain with lists associated to it. Regards Henrik Rasmussen

2 2