- Mailman-users - lists.mailman3.org

hyperkitty web site
by Gelpi Andrea 28 Apr '20

28 Apr '20

Hi, after importing old mm2 messages into mm3 archive I found that hyperkitty dos not show the lists index in home page if FILTER_VHOST = True https://website/mailman3/hyperkitty/ show an empty lists. If I add list/list@domain1 I can see the archive. I think the problem is the domain name example.com that I saw in the upper left corner. If in django administration I rename that site it works. But having more than one domain this is not a solution. what i need is to separate different domains https:/website1/mailman3/hyperkitty shows some lists https:/website2/mailman3/hyperkitty shows other lists Where am I wrong? What have I to change in hyperkitty to have the correct domain shown? Is there a documentation to configure that? Hyperkitty version is 1.2.2 Thank you. -- 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. --------------------------------------------------------------

3 4

How to access my mailman 3 REST API over https and from another machine?
by Shashikanth Komandoor 28 Apr '20

28 Apr '20

Hi, I have setup Mailman 3.3 version and would like to use the REST API by another application. But that application is on another machine and so I need to allow accessibility from another machine also. Along with that as I am trying to access from another machine I need to access the REST API of mailman 3 over https only. Could any one guide me to enable mailman 3 REST API over https and access from another machine other than localhost only ? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 2

MM2 to MM3 on debian 10
by Gelpi Andrea 28 Apr '20

28 Apr '20

Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 mailing lists. I know that not all can work. In my old lists I have email and regular expressions in reject_these_nonmembers and discard_these_nonmembers After importing the list all these email are in non member list. All these email have Delivery status enabled. Does this mean that all of them will receive any message sent to the list? The moderation rule is correct, but if I understood correct Delivery status should be disabled. For migration I followed this link https://docs.mailman3.org/en/latest/migration.html To migrate archives it states to run python manage.py hyperkitty ... I cant' find a manage.py on debian 10 A search shows the only /usr/share/mailman3-web/manage.py exists. Is there any documentation specific for debian? Thank You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

2 3

Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3
by Stephen J. Turnbull 25 Apr '20

25 Apr '20

Shashi, This whole thread is off-topic for the developers list. This list is for development of Mailman, not for teaching people to use it. Read the whole recommended documentation before you ask busy developers to tutor you in very basic things. There's a mailman-users(a)mailman3.org list for users to help each other. All of the Mailman developers who might be willing to answer your questions are there as well, but there are also many experienced users, some of whom have experimented with the REST API who will also help. Please reply there for further help. (Reply-To is set.) That said, there are plenty of URLs in the API documentation. Here's a hint: search for "dump_json". That function takes an URL. You may want https: instead of http: in your URLs, and you may need to change the port from 9001, depending on the configuration of your REST server. Try it with simple GET requests for information first, such as for domains or lists. You can also do these requests with an ordinary web browser, though I don't know what it will do with the JSON-formatted reply. If you don't have domains and lists configured, I suppose the informational requests will come back as empty JSON objects. It should be safe to make them. You can either use Postorius to bootstrap a few example domains, lists, and users, or (the hard way) figure out how to POST appropriate requests. I don't recommend trying to update the backend DBMS by hand; the schema is quite complicated. I don't know how to use curl to update Mailman's databases. That requires a POST request which I have never done with curl. The POST request needs to be valid JSON. The more I think about this, the less I think your idea of using curl is worthwhile, because formatting JSON requests by hand is going to be a real annoyance and a great way to mess up your database with spurious information. You're really going to want programmatic support for this. But that's already all available in Python in the Mailman system. It's up to you, but I feel a responsibility to warn you that using curl is not going to be simpler than learning enough Python to do these things. Regards,

2 1

Bounce processing
by Andrew Hodgson 23 Apr '20

23 Apr '20

Hi, Just upgraded to Mailman 3.3.1 at the beginning of the week and its very refreshing to have bounce processing working after all this time, stops the continued delivery to dud email addresses causing problems with junk email scoring. Anyway after a few days of using this I have noted the following feedback: When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. Thanks. Andrew.

2 1

Changing web access
by Ralf Wiegand 22 Apr '20

22 Apr '20

Hello Members, I am testing mailman3 in a test environment. python manage.py runserver Performing system checks... System check identified no issues (0 silenced). April 22, 2020 - 14:13:57 Django version 2.2.12, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C. tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 6497/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 6404/python How can I change this to have access from any host on my local network. The server running mailman3+hyperkitty+postorius is a rhel7 server without a GUI interface. I also need to give access to our developer on the same subnet. Thank You, Best regards, Ralf Wiegand

3 5

Can't open PID file after start.
by Torge Riedel 22 Apr '20

22 Apr '20

Hi, today there were some package upgrades on my server for python3. Just to be safe I did a "systemctl restart mailman" afterwards. Calling "systemctl status mailman" gave me the following output: mailman.service - GNU Mailing List Manager Loaded: loaded (/opt/mailman/core/mailman.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-04-22 07:01:30 CEST; 6s ago Process: 24178 ExecStop=/opt/mailman/core/bin/mailman.sh stop (code=exited, status=0/SUCCESS) Process: 24180 ExecStart=/opt/mailman/core/bin/mailman.sh start (code=exited, status=0/SUCCESS) Main PID: 24182 (python3) Tasks: 13 (limit: 2335) CGroup: /system.slice/mailman.service ├─24182 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/master -C /opt/mailman/core/mailman.cfg ├─24185 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=archive:0:1 ├─24186 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=bounces:0:1 ├─24187 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=command:0:1 ├─24188 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=in:0:1 ├─24189 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=lmtp:0:1 ├─24190 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=nntp:0:1 ├─24191 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=out:0:1 ├─24192 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=pipeline:0:1 ├─24193 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=rest:0:1 ├─24194 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=retry:0:1 ├─24195 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=virgin:0:1 └─24196 /opt/mailman/core/venv/bin/python3 /opt/mailman/core/venv/bin/runner -C /opt/mailman/core/mailman.cfg --runner=digest:0:1 Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file /opt/mailman/var/master.pid (yet?) after start: No such file or directory Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. Should I treat the PID message as an info or is it an error and something is now broken? The file is there (content is 24182) and timestamp is from the time where I restarted mailman. Best Torge

2 2

Different Mail Domain Cause Key Error
by Brian Carpenter 22 Apr '20

22 Apr '20

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com). I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

3 6

MM3 gateway errors and frequent reboot needs
by hansen＠rc.org 22 Apr '20

22 Apr '20

We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? Please advise. PS: My old MM2 installation could (and did) run without any help. Not so with MM3.

4 3

Mailman Core 3.3.1 release
by Abhilash Raj 19 Apr '20

19 Apr '20

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

1 0