November 2018 - Mailman-users - lists.mailman3.org

Mailman3-Web lots of database queries
by Stefan Tatschner Dec. 10, 2018

Dec. 10, 2018

Hey! I recently set up a mailman3 instance and it works quite nice. I use the debian packages from buster. After running the thing for a few days, I realized an unexpected network load (my postgres database is on a separate machine). Turning the postgres log on revealed that mailman3 constantly queries the database: [...] 2018-11-17 16:33:15.417 UTC [8304] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.385901+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.663 UTC [8305] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.621505+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.664 UTC [8306] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.624011+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.908 UTC [8308] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.870547+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:15.910 UTC [8307] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.871611+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.152 UTC [8310] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.116762+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.154 UTC [8309] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.114878+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.390 UTC [8311] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.358211+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.393 UTC [8312] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.359704+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.634 UTC [8313] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.596602+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.636 UTC [8314] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.598296+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.882 UTC [8315] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.842795+00:00'::timestamptz) LIMIT 1 2018-11-17 16:33:16.884 UTC [8316] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:16.841916+00:00'::timestamptz) LIMIT 1 [...] Is this behaviour intended? Stefan

4 12

Mysql issue in django migrations
by Peter Sørensen Dec. 5, 2018

Dec. 5, 2018

Hi, I have seen others having below problem: File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/recorder.py", line 57, in ensure_schema raise MigrationSchemaMissing("Unable to create the django_migrations table (%s)" % exc) django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table ((1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1")) But haven’t been able to find a proper solution. It’s not a syntax problem. Can anyone help ? Best regards Peter Sørensen/University of Southern Denmark

2 2

HyperKitty/Mailman3 issues
by Florian Schulze Dec. 4, 2018

Dec. 4, 2018

Hi! I tried setting up Scheduled Tasks as described in <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> but the "runjobs" command can't be found. I see the hyperkitty and mailman commands when using "help". The "qcluster" service is working. Using Django 2.1.1 and HyperKitty 1.2.1. Maybe related to that, I have two issues with archives. 1. Changing the archiving setting in the Web-UI to something else than public seems to have no effect. The already archived messages are still accessible in public. 2. Related to 1., how can I remove a list archive without affecting other lists? Regards, Florian Schulze

2 2

Bounce processing via rest api
by Jukka Uusisalo Nov. 23, 2018

Nov. 23, 2018

Hello, I looked rest api documentation and tried find out way to get information about undelivered postings to the list members. I assum, bouncing processing have this information but is it possible get via rest api? Thank you, Jukka

1 0

Rerun emails in the queue/bad
by Kaleb White Nov. 20, 2018

Nov. 20, 2018

How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks.

2 1

Error: 451 Requested action aborted
by Hagen Bauer Nov. 16, 2018

Nov. 16, 2018

Hi I am running mailman in docker and I start to receive this error when my postfix tries to deliver a mail said: 451 Requested action aborted: error in processing (in reply to end of DATA command)) Any idea what is going wrong and where to look for problems? Regards Hagen

2 2

View only-account
by Henrik Rasmussen Nov. 15, 2018

Nov. 15, 2018

Is it possible to create a Mailman 3 account as view only-access Postorius so our help desk can check users and list settings, but not manage the settings? /Henrik Rasmussen

1 0

Changing posting address
by Johannes Winter Nov. 9, 2018

Nov. 9, 2018

Dear list, I'd like to change the sending address of a mailinglist, but when I try to set it via mmclient with ./manage.py mmclient lists=client.lists l=lists[listnumber] l.settings['posting_address']='new name' I get `ValueError: value is read-only`. Is it possible to change this value, or should I use another setting for this objective? Best regards, Johannes Winter

2 1

Setup Mailman3 on shared webhost
by Keyra Nov. 8, 2018

Nov. 8, 2018

Iam trying to setup mailman3 on a shared webhost (with ssh access). I could use pip3.6 install mailman --user and also mailman info But when I try to start mailman using mailman start I will first get the error message TypeError: expected str, bytes or os.PathLike object, not NoneType and when I try it a second (and third etc.) time, it throws Starting Mailman's master runner /usr/bin/python3.6: can't open file '/usr/bin/master': [Errno 2] No such file or directory I didn't get any error messages during installation, so I guess whatever mailman is looking for in /user/bin/master is available in my /home/user/ folder, but I have no idea where and how to tell mailman to look there. For more infos, this is the output of `mailman info` GNU Mailman 3.2.0 (La Villa Strangiato) Python 3.6.5 (default, Apr 10 2018, 17:08:37) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] config file: /var/www/virtual/user/html/var/etc/mailman.cfg db url: sqlite:////var/www/virtual/user/html/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:XXXX

2 1

Hyperkitty - Non-ascii sender address
by Guiseppin Thomas Nov. 4, 2018

Nov. 4, 2018

Hi, I imported some mbox archives in Hyperkitty. I have lot issues like: /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: ('Non-ascii sender address', <email.message.EmailMessage object at 0x7f05f1606048>)// //Non-ascii sender address from "Stéphane blipblop <stlablipblop at gmail.com>" about [HATLAB][It] Re: A débarrasser ! / It's probably because "Stéphane". Some advise to fix it ? Name: HyperKitty Version: 1.2.1 Thanks, Thomas.

3 4