June 2022 - Mailman-users - lists.mailman3.org

Django errors after deleting a thread
by peter＠chubb.wattle.id.au 06 Jul '22

06 Jul '22

After deleting a thread via the web interface (because it's spam), I get lots of messages from hyperkitty E.g. Internal Server Error: /hyperkitty/list/list@domain/top-threads DoesNotExist at /hyperkitty/list/list@domain/top-threads Thread matching query does not exist. Request Method: GET Request URL: https://example.com/hyperkitty/list/list@domain/top-threads Django Version: 2.2.17 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.6 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Wed, 25 Nov 2020 07:12:00 +1100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py" in inner 135. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py" in overview_top_threads 220. 'threads': mlist.top_threads, File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in top_threads 168. return self.cached_values["top_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py" in __call__ 59. return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in get_or_set 376. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py" in <listcomp> 376. return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in get 406. raise self.model.DoesNotExist( Exception Type: DoesNotExist at /hyperkitty/list/devel(a)sel4.systems/top-threads Exception Value: Thread matching query does not exist. Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data

3 4

uwsgi memory usage
by peter＠chubb.wattle.id.au 29 Jun '22

29 Jun '22

Hi Folks, I think there's a memory leak somewhere in the system. Over time, on a relatively small set of lists, I see the uwsgi process grow and grow until the system OOMs. I'm using the Debian packaged mailman3 suite, on the Unstable distribution. This is version 3.3.3. I've reported the bug to the Debian maintainers (who are overloaded...), but was wondering if others had seen this issue. Is it a Debian issue, a local config issue, or a general problem? Peter C

4 4

Hyperkitty failure "Forbidden" - Please check IP-Address assigned to MAILMAN_ARCHIVER_FROM in the settings file
by christopher.claus＠tgcamberg1848.de 29 Jun '22

29 Jun '22

Hi together, i noticed an error during upgrade, which i did not noticed before, but i see no relation to the upgrade itself. Nevertheless the message is very clear, i am not able to solve this issue. My problem ist, that hyperkitty is not working. In mailman.log, you can see this message: Jun 29 13:38:25 2022 (28) ACCEPT: <006501d88bac$b21201f0$163605d0$@mydomain> Jun 29 13:38:28 2022 (32) HyperKitty failure on https://mydomain/hyperkitty/api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) I´m using setting_local.py in web-part with following code: # Try to get the address of Mailman Core automatically. MAILMAN_HOST_IP = gethostbyname('mailman-core') MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) Debugging inside my docker-container, this python-code works fine (hostname etc. are correct): bash-5.0# python3 test.py MAILMAN_HOST_IP 172.18.0.4 MAILMAN_ARCHIVER_FROM ('172.18.0.4',) bash-5.0# I also tried to set MAILMAN_ARCHIVER_FROM directly to the IP not using the list, but there was no change. I think, the problem is located at another place and the error-message took me to the wrong place. Does anybody has an idea where to look at? Best regards, chrclaus

1 1

Run 'manage.py makemigrations' to make new migrations
by christopher.claus＠tgcamberg1848.de 29 Jun '22

29 Jun '22

Hello together, at startup of my docker-container with mailman 0.4.3 i got some warnings to apply some data-model-migrations. I´m very unfamilar with python and django and be not sure how to handle it. Are these warnings from mailman and should i migrate the data-model (and how)? Or should i ignore these message for keeping mailman in a safe state? Best regards, chrclaus System check identified some issues: WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. 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. Your models in app(s): 'postorius' have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

3 3

docker setup
by epi＠epinux.com 28 Jun '22

28 Jun '22

Hi, attempting to install mailman3 on a remote ubuntu server - my docker-compose file looks like: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a /opt/mailman/core/mailman-extra.cfg ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.1.1 lmtp_port: 8024 smtp_host: 127.0.1.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg ``` opt/mailman/web/settings_local.py ``` EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '127.0.1.1' EMAIL_PORT = 25 USE_SSL = False DEFAULT_FROM_EMAIL = "mailman(a)lists.libkml.org" SERVER_EMAIL = "mailman(a)lists.libkml.org" DEBUG = True ALLOWED_HOSTS='libkml.org' ``` I know I am still missing the NGNIX/APACHE settings, but trying to access the service at: libkml.org:8000 I get a django error Invalid HTTP_HOST header: 'libkml.org:8000'. You may need to add 'libkml.org' to ALLOWED_HOSTS. but I have the 'libkml.org' to ALLOWED_HOSTS in both `opt/mailman/web/settings_local.py` and in the dockerfile: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… Can you help me please to understand what I am doing wrong? Thanks!

3 5

What's the difference between (purpose of) reject and ignore
by denis.bitouze＠univ-littoral.fr 27 Jun '22

27 Jun '22

Hi, at a page of the form .../postorius/lists/mylist/held_messages, it is possible to: - Accept - Reject - Ignore messages to be moderated. I didn't find any documentation about the difference between (the purpose of) “Reject” and “Ignore”. Since the list I'm currently moderating suffers from a lot of spammers, I wonder if there is a way to at the same time: - remove the spam from the moderation list (“Reject”? “Ignore”?), - add the emails from the removed spams to the list of banished emails (since copying-pasting each mail to be banished is a pain). Thanks in advance!

5 13

Excluding archives from a mailman3web database backup
by Andy Smith 24 Jun '22

24 Jun '22

Hi, In doing regular database dumps for backup purposes I note that by far the largest quantity of data is HyperKitty's archives. We already keep external archives using the prototype archiver (and some rotation of Maildirs), because we see value in having a simple archive outside of HyperKitty. So, I'd rather not be backing up this data twice. In event of disaster I'd like to be able to do a maildir2mbox on what prototype has written and re-import the resulting mbox file. Is that a realistic proposal? i.e. does a typical maildir2mbox conversion script generate something that "manage.py hyperkitty_import" would be happy with when run on prototype's maildir? If so, is it safe to just exclude every table starting with "hyperkitty_" from the database backup of mailman3web? Dumping only the schema for these, I mean, so that an import would restore empty tables. Thanks, Andy

2 2

How can I clear "Subscription request already pending" status ?
by Axel Rau 24 Jun '22

24 Jun '22

Hi all, I’m getting HTTP Error 409: Subscription request already pending I (as listmaster) would like to subscribe the new member manually, but this fails with above message. Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 2

Docker images with Hyper kitty 1.1.0
by bob B 23 Jun '22

23 Jun '22

Maxking, it looks like the docker images with tags "latest" and more importantly "0.4.2" which I believe is supposed to be the latest version, have mailman-hyperkitty 1.1.0 installed, which does not work with the installed Hyperkitty version, so archiving is broken? is this correct? Any eta on when this will be corrected? it looks like "rolling" has mailman-hyperkitty 1.2.1 but the notes say to consider rolling as beta software. Thanks

3 3

I'm new to mailman
by LIULIANG 23 Jun '22

23 Jun '22

Hello everyone, My name is Liang Liu. Currently, I am a GSoC student and I am developing a list configuration tool for mailman. You can learn more about what I am doing by following the link below. https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202022#List_Configura… If you have good suggestions feel free to send me an email. As time goes on, I maybe asking some questions of what the user needs. And I will be consulting with developers on how to get work done. Hope we have a good summer. Yours sincerely, Liang Liu

1 0