Search results for "Postorius" - Mailman-users

Re: Source Installation Assistance

by actionmystique＠gmail.com

I have built python3-django-hyperkitty for Ubuntu/Debian distributions from the gitlab hyperkitty sources with the commit that fixes the issue(266): use an errorless test to determine the existence of the table social_auth_usersocialauth. It passes the test on Ubuntu focal with flying colors: ``` # python3 manage.py makemigrations # python3 manage.py migrate "No changes detected", "Operations to perform:", " Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount", "Running migrations:", " Applying contenttypes.0001_initial... OK", " Applying auth.0001_initial... OK", " Applying account.0001_initial... OK", " Applying account.0002_email_max_length... OK", " Applying admin.0001_initial... OK", " Applying admin.0002_logentry_remove_auto_add... OK", " Applying admin.0003_logentry_add_action_flag_choices... OK", " Applying contenttypes.0002_remove_content_type_name... OK", " Applying auth.0002_alter_permission_name_max_length... OK", " Applying auth.0003_alter_user_email_max_length... OK", " Applying auth.0004_alter_user_username_opts... OK", " Applying auth.0005_alter_user_last_login_null... OK", " Applying auth.0006_require_contenttypes_0002... OK", " Applying auth.0007_alter_validators_add_error_messages... OK", " Applying auth.0008_alter_user_username_max_length... OK", " Applying auth.0009_alter_user_last_name_max_length... OK", " Applying auth.0010_alter_group_name_max_length... OK", " Applying auth.0011_update_proxy_permissions... OK", " Applying sites.0001_initial... OK", " Applying django_mailman3.0001_initial... OK", " Applying django_mailman3.0002_maildomain... OK", " Applying django_q.0001_initial... OK", " Applying django_q.0002_auto_20150630_1624... OK", " Applying django_q.0003_auto_20150708_1326... OK", " Applying django_q.0004_auto_20150710_1043... OK", " Applying django_q.0005_auto_20150718_1506... OK", " Applying django_q.0006_auto_20150805_1817... OK", " Applying django_q.0007_ormq... OK", " Applying django_q.0008_auto_20160224_1026... OK", " Applying django_q.0009_auto_20171009_0915... OK", " Applying socialaccount.0001_initial... OK", " Applying socialaccount.0002_token_max_lengths... OK", " Applying socialaccount.0003_extra_data_default_dict... OK", " Applying hyperkitty.0001_initial... OK", " Applying hyperkitty.0002_auto_20150311_0913... OK", " Applying hyperkitty.0003_thread_starting_email... OK", " Applying hyperkitty.0004_archived_date_and_subject... OK", " Applying hyperkitty.0005_MailingList_list_id... OK", " Applying hyperkitty.0006_thread_on_delete... OK", " Applying hyperkitty.0007_allauth_20160808_1604... OK", " Applying hyperkitty.0008_django_mailman3_profile... OK", " Applying hyperkitty.0009_duplicate_persona_users... OK", " Applying hyperkitty.0010_email_sender_name... OK", " Applying hyperkitty.0011_email_parent... OK", " Applying hyperkitty.0012_thread_order_null... OK", " Applying hyperkitty.0013_mailinglist_id_1... OK", " Applying hyperkitty.0014_mailinglist_id_2... OK", " Applying hyperkitty.0015_mailinglist_id_3... OK", " Applying hyperkitty.0016_auto_20180309_0056... OK", " Applying hyperkitty.0017_file_attachments... OK", " Applying hyperkitty.0018_threadcategory_color... OK", " Applying hyperkitty.0019_auto_20190127_null_description... OK", " Applying hyperkitty.0020_auto_20190907_1927... OK", " Applying postorius.0001_initial... OK", " Applying postorius.0002_auto_20160210_0721... OK", " Applying postorius.0003_drop_addressconfirmationprofile... OK", " Applying postorius.0004_create_email_template... OK", " Applying postorius.0005_auto_20180707_1107... OK", " Applying postorius.0006_auto_20180711_1359... OK", " Applying postorius.0007_auto_20180712_0536... OK", " Applying sessions.0001_initial... OK", " Applying sites.0002_alter_domain_unique... OK", " Applying socialaccount.0004_openidnonce_openidstore... OK" ``` Anyone can grab the binary package on my [Ubuntu Focal PPA](https://git.sdxlive.com/PPA/tree/Ubuntu/pool/unstable/p/python3-django… or [Debian Bullseye Repository](https://git.sdxlive.com/DR/tree/Debian/pool/unstable/p/python3-…. python3-django-hyperkitty has been built for the latest Ubuntu & Debian development distributions (focal & bullseye), but it should be possible to use them on earlier distributions since there is no specific dependencies.

6 years, 9 months

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 But it’s not in 1.3.5: https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 Thats ok, I’m going to 1.3.6 in a few days so that should solve my issue. -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:39 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 7:27 PM, Simon Coggins wrote: > Oops sorry I hit send to soon. If I try to go > to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> I get a 404, it > looks like unsubscription_requests > <http://listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests>> isn’t in my > urls.py list for Postorius? It should be. It was added by https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…<https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3…> -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 10 months

Re: hello， Discussion on how to subscribe to themailing list

by Stephen J. Turnbull

朱超 writes: > 1. It is not the MTA that refuses to send emails because the > recipient's mailbox is too long, but the MUA that refuses to > send the email because the recipient's mailbox is too long. That's still non-conforming to RFC 821, published in 1982. Seriously, those mail clients are garbage and I have no sympathy for their users. We're certainly willing to make some changes to Mailman to make things a little easier for mailing list owners who have to deal with such users, but there's no excuse for using those MUAs in 2023. > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, > but he reported 404. If you mean that literally, of course it did. example.com, and its siblings in the org, net, and edu domains, as well as all subdomains, are domains reserved for examples in documentation. They all resolve to the same IP (owned by IANA), which simply provides a web page explaining what those domains are for. There's no Mailman there. :-) For that to get a response from Postorius, at minimum you need to substitute your Mailman web host for "www.example.com", and the list's ID (usually the same as the posting address with "." substituted for the "@") for $list_id. You may also need to change the URL path, depending on the top-level urls.py you use for Postorius. > 2. It is recommended to modify postorius, in order to keep the > logic function of the underlying mailman-core unchanged, More important than the detailed functions of mailman-core are the original requirements and design. Core should handle email (both in and out), and Postorius should handle web requests. It's asking for trouble to have core send mail to confirm subscription requests by mail, and Postorius to send mail to confirm subscription requests by web. Among other things it violates "Don't Repeat Yourself": if we (or you) change the confirmation template in core, we (or you) need to also change the confirmation template in Postorius. But it's very easy to forget, and an annoyance for reviewers to check. It's possible that the other core devs will overrule me on this, but you shouldn't hold your breath waiting for that. I've been very good at channeling the consensus of the devs for around 20 years now. :-) Steve

3 years, 8 months

Hyperkitty stuck files

by zoltan＠circle-interactive.co.uk

Hi, I have a mailman3 setup in venv with python 3.11.2 mailman 3.3.9 mailman-hyperkitty 1.2.1 I feel I have read a lot about issues with stucked files in spool directory still I am not able to proceed with debugging in my case. Ideas would be welcome and appreciated. Thanks This is the error in archiver.log Jul 09 10:56:12 2024 (47531) HyperKitty archiver processing queued filebase: 1720522497.980487+a88492922feca24ced15594a5ec16556195 6f3ad Jul 09 10:56:12 2024 (47531) hyperkitty archiver: sending message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/archive: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> (500) Jul 09 10:56:12 2024 (47531) Could not archive the message with id <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) archiving failed, re-queuing (mailing-list act.lists.contextualscience.org, message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com>) Jul 09 10:56:12 2024 (47531) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Jul 09 10:56:12 2024 (47531) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html>

2 years, 2 months

Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/28/25 12:31, Arte Chambers via Mailman-users wrote: > > I'm getting the following error when using mass subscription on a testing > list with a custom template loaded for [list:user:notice:welcome] > ``` > HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read timed > out. (read timeout=5) > ``` It appears you are setting the template in Postorius and there is an issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. It looks like this is something like ``` POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' ``` and that connection is timing out. Try setting just the scheme and host for access to Postorius. I.e., if you access Postorius at a URL like https://www.example.com/mailman3/, try ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://www.example.com/' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Moderation action "None" is misleading

by Mark Sapiro

On 2/4/25 02:51, Markus Grandpré wrote: > Dear List, > > I find the use of the term 'None' (or 'Kein' in the German translation; > see attachments) in the 'Moderation action' column of the member list > misleading, as the term suggests that no moderation action is applied to > the respective member. > > However, this is not necessarily the case. If you check a member’s > "Administration options / Moderation" setting, a moderation action, such > as "Moderation" or "List default", may be in effect. This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/811 See the UI changes at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Held messages page not rendering the message

by Andreas Schamanek

On Sat, 25 Mar 2023, at 17:32, Mark Sapiro wrote: > On 3/25/23 10:01, mike-mailman(a)earth.li wrote: >> >> This seems like maybe its a CSS issue? The class of the held-message-modal >> is "modal fade show" but I am not sure where that is or should be defined >> (or even if I'm looking at completely the wrong thing. >> >> Anyone able to suggest where to look? > > This is bootstrap. See > https://www.w3schools.com/bootstrap/bootstrap_modal.asp > > One possible issue is if you have older bootstrap cached in your browser it > could cause problems. It's unlikely considering you've tried different > browsers, but try clearing your browser cache. I had the exact same issue. As you guessed, Mark, it was related to bootstrap, though not from the browser cache but a mixup of versions served by the server. Also thanks to your research, Mike, I found that my Apache server has Alias /mailman3/static /var/lib/mailman3/web/static /var/lib/mailman3/web/static included a directory "postorius" which served bootstrap.min.css v3.3.5 whereas on my server v4.0.0 is included in python3-django-postorius 1.3.4-2+deb11u1 cd /var/lib/mailman3/web/static mv postorius postorius.bak ln -s /usr/share/python3-django-postorius/static/postorius fixed it for me. There's also a Debian bug report for it: https://bugs.debian.org/1010273 -- -- Andreas :-)

3 years, 5 months

Re: Installing MM3 requires Django<1.11

by Mark Sapiro

On 04/12/2017 02:22 AM, Henrik Rasmussen wrote: > Two questions regarding Mailman 3 installation: > > 1) > The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. That link doesn't belong there. Mailman doesn't use Django to send mail. > According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. > > According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". > > In what file should I change the mail settings then? Nothing in <https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends> or <https://www.webforefront.com/django/setupdjangoemail.html> is relevant to Mailman. A more appropriate discussion is at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> > 2) > While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". > > As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. > > *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty This is an issue. The various setup.py files for django-mailman3, hyperkitty and postorius all have Django>=1.8 as a requirement. Only postorius also has Django<1.11. django-mailman3 and hyperkitty should have that restriction too. I have submitted <https://gitlab.com/mailman/django-mailman3/issues/4> and <https://gitlab.com/mailman/hyperkitty/issues/128> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 5 months

Postorius extremely slow on some of the mailinglists

by Eric Broens

Hi, Postorius became extremely slow recently on some of our mailinglists, but not on all of them. Postorius even times out when opening some of them (https://<hostname>/postorius/lists/<mailing_list>.<domain>/) and shows the message "Mailman REST API not available. Please start Mailman core." This only happens when I am logged in (as administrator), but not when I am not logged in. It seems to be independent on the number of subscribers on the particular mailing list. Below you'll find an extract from the logs for a case where it timed out, and for a case where the page showed up after a long time. Mainly "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" takes a long time. There is nothing unusual going on regarding database queries, and mails are delivered normally. Any idea why this happens and how it can be solved? [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 378 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2283 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3107 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [2025-02-05 19:05:14 +0100] [1612] [CRITICAL] WORKER TIMEOUT (pid:1653) [2025-02-05 19:05:14 +0100] [1653] [INFO] Worker exiting (pid: 1653) [2025-02-05 19:05:15 +0100] [64429] [INFO] Booting worker with pid: 64429 [07/Feb/2025:13:42:14 +0100] "POST /3.1/lists/find HTTP/1.1" 200 18226 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 414 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2337 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3232 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>.<domain>/member/<my.email>%40<mydomain> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Thanks, Eric

1 year, 7 months

postorius / adjusted settings menu

by Andreas Barth

Hi together, I want to adjust the settings menu to reduce to the options really needed. The easiest way would be to edit src/postorius/views/list* but I don't think that's a good idea. So what comes to my mind is to have some variable in the configuration that contains the menu items and - if set - the submenus. E.g. the following: { 'list_identity': ['!gateway_to_mail', '!gateway_to_news', '!linked_newsgroup', '!newsgroup_moderation', '!nntp_prefix_subject_too' ], 'automatic_responses', 'alter_messages', 'dmarc_mitigations', 'digest', 'message_acceptance', 'archiving', 'subscription_policy', 'bounce_processing' } would express: default menu and just remove the mentioned items. Of course, something like ['advertised', 'description', 'info', 'display_name', 'subject_prefix'] would work as well. Resorting should also be possible, so something like { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } would give a very small list of items to select from. What do you think about the idea? Andi

5 years, 6 months

Mailman-users search results for query "Postorius"