- Mailman-users - lists.mailman3.org

Mailman3-Web lots of database queries
by Stefan Tatschner 10 Dec '18

10 Dec '18

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

Re: [Mailman-Users] Mailman 3 on Ubuntu 18.04
by Odhiambo Washington 09 Dec '18

09 Dec '18

On Sun, 9 Dec 2018 at 22:37, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/9/18 10:14 AM, Odhiambo Washington wrote: > > > > In my quest to run Mailman3, I obtained a VM running Ubuntu 18.04 and > > started on getting to run Mailman3. > > I found this link -> https://github.com/iomarmochtar/mailman3_ei > > It has instructions which looked fairly simple to get Mailman3 installed. > > However, I did encounter some hitches since the script is not meant for > > Ubuntu. > > > First, a more appropriate list for Mailman 3 is > mailman-users(a)mailman3.org > <https://lists.mailman3.org/mailman3/lists/mailman-users@mailman3.org/>. > I am shifting to that list, after this. > > Also, we find it very difficult to address issues arising from third > party packages and how-tos. See <https://wiki.list.org/x/12812344>. > > And, there is a Mailman 3 package for Debian/Ubuntu > > apt install mailman3-full > In all my searching, I never found this in any documentation. I must have been searching in the wild, or my FreeBSD-mindedness got me stuck to containers and VENVs. > > With a few runs and observing the logs and modifying the script at every > > step it encountered and error, I finally managed to install Mailman3. It > > seems this is what you guys call a virtual environment in the Linux > world? > > :-) > > > I think the virtual environment in this case is a Python thing, not a > Linux thing. > I agree with you on that. > <snip> > > > Much of what I snipped is specific to > <https://github.com/iomarmochtar/mailman3_ei>, the details of which I'm > not interested in learning. > That is fine. I have put it aside for now. > > > >>From this point now is where I need help - serious help in smoothening > > things up and getting to understand these venv stuff! > > > > So I did run 'service mailman3 start' but this seems to be waiting for > too > > long to drop me back into the CLI. > > I also run 'systemctl start supervisord' and that seems to work. What I > am > > not sure is whether 'systemctl stop supervisord' actually does what it is > > expected to do because after I execute it, I still see processes running > > that I think are related. > > > > So far, I have been able to access the webUI on my VM using > > https://N.N.N.N:9090 > > I created a domain. > > But when I create a test list, I get an error - and I do not have a clue > > which logfile would have the error details - nginx or mailman... (I am > 100% > > new to nginx). > > > The nginx logs generally aren't too useful. Both Mailman core and Django > write logs. Core's log is probably in var/log/mailman.log where is > defined in mailman.cfg as var_dir. Django's log is defined in Django's > settings in the LOGGING setting. > Which file contains Django's settings? > > So now, I am stuck at: > > 1. Creating the mailing list > > 2. Getting to know whether the archiver is installed and running > > 3. Knowing is there are cron jobs to be running (Mailman2 type of > thinking!) > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs > > > and > < > http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required > > > Great to see that. I'll read and see if I make heads or tails of the writeup. > > Ultimately I need to figure out: > > 1. How the mailman queue runners are started and stopped > > mailman start > Why not systemctl mailman start?? Just wondering, as that is what I am seeing is common in Ubuntu. Does this make the components start after a reboot? > > 2. Migrate s few lists from Mailman2 to this Mailman3 > > mailman import21 > <django management> hyperkitty_import > Please show me where that is documented. I have to pull my lists from an old machine to this new one. > > 3. Mailman3 should use MySQL storage and Exim4 as the MTA (I have > > configured these bits in mailman.cfg) > > > You also need to configure MySQL in Django. See the DATABASES setting in > the Django settings. > So, when you talk about Django settings, you are referring to mailman.cfg file??? :-) I have spent all my weekend till now, trying to figure all this out. Life seems a little easier with mm2.x .... Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 1

Do not send email "The results of your email commands"
by erlonmz＠hotmail.com 07 Dec '18

07 Dec '18

Hello guys. Have to configure the mailman3 for not to send the e-mail " The results of your email commands" when an email is sent to "-leave@" and "-join@" ?? Sorry for my English, i from another country.

3 2

What is the difference between Mime Digest and Summary Digest in Mailman 3.2.0?
by Henrik Rasmussen 05 Dec '18

05 Dec '18

Having tried both Outlook and Gmail, there doesn't seem to be any visible difference between Mime Digest and Summary Digest. Of cause Gmail shows both index and all posts inline while Outlook shows both index and all posts as attachments, but overall the two digest types doesn't seem different from each other. Is that corrent or did I miss something? /Henrik Rasmussen

2 1

Mysql issue in django migrations
by Peter Sørensen 05 Dec '18

05 Dec '18

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 04 Dec '18

04 Dec '18

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 23 Nov '18

23 Nov '18

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 20 Nov '18

20 Nov '18

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 16 Nov '18

16 Nov '18

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 15 Nov '18

15 Nov '18

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