I assume this is by design, but is it correct that a list owner, who are not member, will always be allowed to post to the list, even though "Default action to take when a member posts to the list" and "Default action to take when a non-member posts to thelist" are both set to "Hold for moderation"? The owner is set as also moderator, by the way, which seems redundant.
I have a list administrator who would like to be moderated when sending to the list, but there is no Member Options on Owners (nor Moderators).
A workaround may be to create a new account for the owner and let the current owner be member instead of owner, as she will then be moderated.
I am new in the list. I have been looking for this topic in the archives
in order to avoid duplicate, but I could not find any thread.
According to the new GDPR rules, lists owners need to have a
confirmation from subscribers, and this is easy to do with Mailman 3.
What I can't figure out is how to save all the confirmation emails
received from users.
I only see the confirmations commands emails in the logs,
Is there another place/way to store them?
For GDPR compliance it is important to be able to demonstrate that you
received the confirmation, in case you may need it in the future.
Tu nube en tus manos
Mailman Core 3.2.2 is released and available on PyPI.
This is a regular bugfix release and I had to do that to fix a version constraint
which pulled in a pre-release of a dependency (falcon) when installed via pip
and caused the default install to break.
There are few other changes included in this release, including a big refactor
of error reporting in Core's REST API. All the error responses are now correctly
formatted as JSON with more information about the error. For example, invalid
inputs for Enum data types return the valid options. Other error message are
now generated from the input validtor and will be more informative.
REST API also accepts input as JSON formatted body, alongside the
A full list of changes are available here:
This release supports Python 3.5-3.7.
Thanks very much to all the contributors involved in this release.
Abhilash Raj (maxking)
in the settings of a mailing list I can choose two archivers: "Hyperkitty" and "prototype". What is this archive "prototype" and how can I disable/remove/deinstall it? And how can I disable archiving at all, so no archiver can be chosen in the settings.
I've had encountered this situation now twice: mail is being stuck in
"out" queue and nothing in the logs indicates the issue. Is there a way
to ask mailman-core politely to attempt delivery (perhaps with increased
debugging in the logs) *without* restarting the core (which does solve
*this* problem but creates other problems, like availability of the
mailman as a whole)
Sr System and DevOps Engineer SoM IRT
how can I disable user registration? There are only two users, me - the admin - and an additional owner/moderator. The list setup we use is completely managed by the owner/moderator (about 100 mail adresses per list).
I've successfully set up mailman3 in a test environment and deleted a test list which I only used for some basic tests. Looking at the archiver, the archive is still there and I haven't found a way to delete it. Although I am logged in as admin.
Is there a (non-) official way to delete the archive? I want a clean environment for the later user to test mailman3.
Thanks and regards
I have been working on a new sub-project Mailman Web. This project basically combines Postorius and Hyperkitty together in a single package which you can easily use to serve Mailman's web interface.
The basic motivation behind this was to make it simpler for people to install the web interface *and* make it easier for people to configure Mailman's web ui.
Both Postorius and Hyperkitty are based on Django Web Framework, which uses settings.py as its default configuration language. While it is quite convenient for Python developers to be able to put Python statements in configuration to join/edit/configure settings. However, I think a traditional INI, or TOML style configuration is easier for non-developers without having to worry about PYTHONPATH, valid Python sytax etc, etc.
For this reason, I decided to combine all the projects together into a Django project which can be easily installed and run:
$ pip install mailman-web
# Export Settings for commands to just work.
$ export DJANGO_SETTINGS=mailman_web.settings
$ django-admin migrate
$ django-admin runserver
This should get you default settings for running. If you want to customize your installation, which you almost always would need to in a prod environment, you can create a config file at one of these locations (which are searched in following order):
Note that we support only TOML as the configuration language because of its simplicity. I would have loved to use INI, like Mailman Core, but it turns out to be way too simple to represent more complex data structures like maps and tables, that is commonly used in Django's Settings.
This project is currently in alpha stage (I created it today!), but can be installed with pip and in my basic tests works. There isn't much in the project itself beyond some configurations.
I also took this opportunity to document all the settings that are used in Mailman Web (both Postorius and Hyperkitty) together. This is documented in code and so I really hope that it won't go out of date like many other places ;-) Improvements to docs is very welcome, just a modification of a comment and is quite easy to propose right in your
web browser using Gitlab!
Any questions, comments or suggestions are welcome. You can open issues for feature requests on gitlab too.
Abhilash Raj (maxking)
after adding a new moderator to a list I get the following message in a green box:
%(email)s has been added with the role %(role)s
Looks like the placeholders are not resolved (correctly).
Should I report this somewhere as a bug?
Mailman Core Version GNU Mailman 3.2.0 (La Villa Strangiato)
Mailman Core API Version 3.0
Mailman Core Python Version 3.6.7 (default, Oct 22 2018, 11:32:17) [GCC 8.2.0]