March 2019 - Mailman-users - lists.mailman3.org

Daily Cronjob fails
by Stefan Tatschner June 8, 2019

June 8, 2019

Hey hey, I applied a recent Update from Debian Buster, und this night a received an email about a failing cronjob. The traceback can be reproduced using: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) psycopg2.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 35, in execute sync_with_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 131, in sync_with_mailman mlist.update_from_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 192, in update_from_mailman self.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 808, in save force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 838, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 905, in _save_table forced_update) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 955, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 667, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1204, in execute_sql cursor = super(SQLUpdateCompiler, self).execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 899, in execute_sql raise original_exception File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 889, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). END TRACEBACK Appearently there is something wrong with the database. Is there anything what I can do about this? Running the migrations doesn't help: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks! Stefan

3 3

Moderate mails from owner
by Henrik Rasmussen May 7, 2019

May 7, 2019

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. /Henrik Rasmussen

4 16

GDPR - save subscriptions confirmation emails
by contact＠maadix.net May 1, 2019

May 1, 2019

Hi, 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. Bests Maddish -- *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

3 4

Mailman Core 3.2.2 is now out
by Abhilash Raj April 14, 2019

April 14, 2019

Hello Everyone, Mailman Core 3.2.2 is released and available on PyPI[1]. 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 x-www-form-urlencoded. A full list of changes are available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 This release supports Python 3.5-3.7. Thanks very much to all the contributors involved in this release. [1]: https://pypi.org/project/mailman/ -- thanks, Abhilash Raj (maxking)

2 3

Archiver "prototype" and disabling archiving at all
by Torge Riedel April 7, 2019

April 7, 2019

Hi list, 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. Best regards Torge

3 4

mail stuck in "out" queue
by Dmitry Makovey March 30, 2019

March 30, 2019

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

2 1

Delete archive of mailing list
by Torge Riedel March 28, 2019

March 28, 2019

Hi 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 Torge

2 2

Introducing Mailman Web project
by Abhilash Raj March 26, 2019

March 26, 2019

I have been working on a new sub-project Mailman Web[1][2]. 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): - /etc/mailman-web.toml - /etc/mailman3/mailman-web.toml - ./mailman-web.toml Note that we support only TOML as the configuration language[3][4] 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[5] 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[6]. 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[1] too. [1]: https://gitlab.com/mailman/mailman-web [2]: https://mailman-web.readthedocs.io/en/latest/ [3]: https://github.com/maxking/django-settings-toml [4]: https://github.com/toml-lang/toml [5]: https://pypi.org/project/mailman-web/ [6]: https://mailman-web.readthedocs.io/en/latest/settings.html -- thanks, Abhilash Raj (maxking)

2 6

Configuring the List-Archive and Archived-At headers
by Ralph Seichter March 25, 2019

March 25, 2019

With archiving enabled, mail is sent with headers like the following: Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> List-Post: <mailto:foo-users@lists.example.com> List-Subscribe: <mailto:foo-users-join@lists.example.com> The 'mailto:' entries are fine, but I need all 'https:' links to be prefixed with https://lists.example.com instead of https://example.com . Does Mailman extract CN parts from the SSL certificate to populate the header values (that would explain 'example.com' in my tests), or is this something I can influence using configuration parameters? I searched the docs for Mailman Suite and HyperKitty, but did not find an answer. -Ralph

5 9

Non resolved placeholders in action message
by Torge Riedel March 23, 2019

March 23, 2019

Hi, 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] Best regards Torge

2 1