Search results for "Postorius" - Mailman-users

Re: Mailman upgrade results in page not found error

by Guillermo Hernandez (Oldno7)

El 3/11/22 a las 14:00, Andrew Hodgson escribió: > Hi. > > Just doing the Mailman suite upgrade on my small installation I use for test purposes. > > Steps include: > Run backup script > Stop services > Mv venv venv-old > python3 -m venv --system-site-packages --symlinks venv > source venv/bin/activate > pip install -U pip > pip install mailman mailman-hyperkitty hyperkitty postorius whoosh > deactivate > ./bin/Django-admin collectstatic > ./bin/Django-admin migrate > > At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. I found the same error, I modified urls.py in the way below: ### from django.conf import settings ### mod. 30/10/22 ###from django.conf.urls import include, url from django.conf.urls import include from django.urls import re_path as url ##### Leaving the rest of original urls.py lines unmodified. > > Once services were up everything worked as expected except for the web page. If you go tohttps://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of havinghttps://lists.hodgsonfamily.org going to the correct place? > > Urls.py: > # -*- coding: utf-8 -*- > # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. > # > # This file is part of Postorius. > # > # Postorius is free software: you can redistribute it and/or modify it under > # the terms of the GNU General Public License as published by the Free > # Software Foundation, either version 3 of the License, or (at your option) > # any later version. > # > # Postorius is distributed in the hope that it will be useful, but WITHOUT > # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or > # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for > # more details. > # > # You should have received a copy of the GNU General Public License along with > # Postorius. If not, seehttp://www.gnu.org/licenses/. > > > from django.conf.urls import include > from django.contrib import admin > from django.urls import path, reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('accounts/', include('allauth.urls')), > path('admin/', admin.site.urls), > ] > > Thanks. > Andrew. > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 10 months

User settings triggers error

by Mark Dadgar

If one of my users (including admin) goes to their user drop-down in the upper-right of Postorius and clicks Mailman Settings, it triggers an error: Here’s the error log: Internal Server Error: /mailman3/postorius/accounts/subscriptions/ KeyError at /postorius/accounts/subscriptions/ 'file' Request Method: GET Request URL: https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/ <https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/> Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.2 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: Tue, 16 Jun 2020 10:31:56 -0700 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', 'django_mailman3.lib.auth.fedora') 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/django/contrib/auth/decorators.py" in _wrapped_view 21. return view_func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/user.py" in user_subscriptions 307. memberships = [m for m in mm_user.subscriptions] File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py" in subscriptions 62. for address in self.addresses: File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __iter__ 221. for entry in self.rest_data: File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data 197. response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call 99. raise HTTPError(url, response.status, content, response, None) During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/postorius/middleware.py" in __call__ 39. return self.get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 36. response = response_for_exception(request, exc) File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in response_for_exception 91. log_response( File "/usr/lib/python3/dist-packages/django/utils/log.py" in log_response 222. getattr(logger, level)( File "/usr/lib/python3.8/logging/__init__.py" in error 1463. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.8/logging/__init__.py" in _log 1577. self.handle(record) File "/usr/lib/python3.8/logging/__init__.py" in handle 1587. self.callHandlers(record) File "/usr/lib/python3.8/logging/__init__.py" in callHandlers 1649. hdlr.handle(record) File "/usr/lib/python3.8/logging/__init__.py" in handle 950. self.emit(record) File "/usr/lib/python3/dist-packages/django/utils/log.py" in emit 119. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/usr/lib/python3/dist-packages/django/views/debug.py" in __init__ 254. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.8/tempfile.py" in __getattr__ 607. file = self.__dict__['file'] Exception Type: KeyError at /postorius/accounts/subscriptions/ Exception Value: 'file' Request information: USER: admin GET: No GET data POST: No POST data FILES: No FILES data Anyone got a solution to this? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 3 months

Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I have had this working before, so I guess it's a simple setup error. When I send a message from the Postorius interface, it is neither sent out or stored. I briefly see this message: "Your reply has been sent and is being processed.", and then nothing happens. I have installed maxking's docker-mailman and copied my old setup with basic stuff like passwords and such. The only new thing is that I'm now running in userspace by putting in /etc/subuid and subguid: mailman:10000:65536 and in /etc/docker/daemon.json: { "userns-remap": "mailman" } So I get the following ownership in /opt/mailman: drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core drwx------ 19 10070 10000 4096 nov. 21 09:27 database drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web (I have created a user named mailman with uid 10100 so, in reality, it says "mailman" there instead of 10100 but I guess that is irrelevant here)

8 years, 10 months

Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank you, Mark. I have Postorius Version 1.3.4 I see no 'Users' in Postorius, but I do see it in Django. I'll assume that my Postorius is out of date and will take steps to update it. Yours, Allan On 1/11/22, 10:38 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- Mark Sapiro <mark(a)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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

Re: Auth question

by David Krantz

On Thu, Mar 30, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > To be more specific, the projects that are required for a fully > functioning Mailman installation with Postorius and Hyperkitty are > > Mailman (the core) > > Hyperkitty (the archiver) > > Postorius (the web list management UI) > > django-mailman3 (common django things used by Postorius and Hyperkitty) > > MailmanClient (python bindings for the core REST API used by Postorius > and Hyperkitty) > > HyperKitty - Mailman plugin (plugin for the core to communicate with > Hyperkitty) > I tried to upgrade today. The result is a broken install which fails when trying to upgrade the database. $> ./bin/mailman-post-update [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() django.db.utils.IntegrityError: update or delete on table "auth_user" violates foreign key constraint "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on table "social_auth_usersocialauth" DETAIL: Key (id)=(3) is still referenced from table "social_auth_usersocialauth". I have tried to drop and recreate the databases but I get the above result anyway. The description in https://wiki.list.org/DOC/Mailman%203%20installation%20experience is very hazy. The process of symlinking in libraries is fiddly to say the least. I get mailman to start but not any web interface. I have not tested mailman so if it works rather than just start I do not know. There is a description for a clean install for development at http://docs.mailman3.org/en/latest/devsetup.html, but I suspect that it isn't usable for anything other than development. I have read it parallell to try to interpret the installation experience description which in turn describes more of what I am trying to do. No luck though. regards // David

9 years, 5 months

Re: mailman.cfg (use_https: yes) fails

by Mark Sapiro

On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > In this context I faced a strange behavior: > > In the database mailman3web in table django_site are listed several > domains, either in the django-domain-management site > https://[mydomain]/mailman3/admin/sites/site/ > > id domain name > 1 example.com Example.com > 2 [mydomain-1] [mydomain_name_1] > 3 [mydomain-2] [mydomain_name_2] > 4 [mydomain-3] [mydomain_name_3] > > In case I delete line 1 with the id 1, in the database or in the > django-web-site, postorius fails to work. After re-inserting this line, > postorius works again. In your settings.py, you probably have SITE_ID = 1. Thus, when you delete the site with id = 1, Postorius fails. You need to set SITE_ID to an existing site in settings_local.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 16:41 schrieb Brian Carpenter: > On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: >> In case it matters, I'm trying to moderate the list using the "root" >> account. Discarding works, but when I try to either accept or reject a >> message, there is a timeout. > > Is there an error message displaying in Postorius or do you receive an > Apache timeout error? Neither. The browser times out. >When you say root account, do you mean the Django > superuser account? I guess? It's the one I created using "python manage.py createsuperuser". > Also have you made sure all of the permissions are > owned by the mailman user in /opt/mailman? Right now everything is running as root (except for Apache). I realized too late that I should've used a mailman user. Could that be the reason for the issue?

6 years

Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:48 AM, Marc SCHAEFER wrote: > > May I just modify those files, and is there any way to see, in the web GUI, > where those files are referenced? Yes, you may modify them. The search algorithm for templates is described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… however, this is only for templates which have no entry or a mailman:/// entry in the template table in the database. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > In the database itself, the template table is empty (as seen in the GUI) and I > did not see the text "web_page_url" in a dump of the database, so I have some > issues to understand how this is used by Mailman (except direct file access > to /var/lib/mailman3/templates?) It is by direct access following the search algorithm. If you are looking at templates in Postorius, these can be created and will place the template in the postorius_emailtemplate table in the database and an entry in the templates table with a URI beginning with the POSTORIUS_TEMPLATE_BASE_URL setting to retrieve the template via the Postorius API. The Postorius template UI should show the current value for a template not yet set in Postorius, but it doesn't. See https://gitlab.com/mailman/postorius/-/issues/366. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Re: Missing bits of French translation

by Mark Sapiro

On 5/12/26 17:30, iMark wrote: > > 3. Page text fails. eg. > ENGLISH: You have to sign in to visit the archives of this list. > FRENCH: Is in English. > > Looking at the .po file ... > > /opt/mailman/venv/lib/python3.11/site-packages/mailman/messages/fr/LC_MESSAGES/mailman.po > > "PO-Revision-Date: 2024-06-25 17:09+0000\n" That file is out of date. It may or may not be from the latest Postorius released version but it has been subsequently updated for the next release. That particular string is marked fuzzy in the current .po - see <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/…> It is marked fuzzy because the msgid was changed at some point from ``` msgid "You have to login to visit the archives of this list." ``` to ``` msgid "You have to sign in to visit the archives of this list." ``` The translations are managed at Weblate. The particular French translation for Postorius is at <https://hosted.weblate.org/projects/gnu-mailman/postorius/fr/>. The above string is one of 19 that are marked for edit. You are more than welcome to create an account at Weblate and fix whatever needs fixing in the French translation and Weblate will submit a merge request to update the .po on GitLab. We would be grateful for your help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

Re: Moderate mails from owner

by Mark Sapiro

On 3/21/19 3:02 AM, Malcolm Austen wrote: > > My only experience of MM3 is with Ancestry's 'RootsWeb' installation. > From the emails I can see a header "X-Mailman-Version: 3.1.0" but I > can't find anything to identify Postorius which is the only interface I > have to the system. Isn't there a footer at the bottom of wach page with something like: Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 > From symptoms seen and described by others, I have deduced that the > Postorius admin-per-user moderation options of "Default processing" and > "List default" mean that a user may be set (by default on the rootsweb > system!) to use the system default moderation settings rather than the > list default settings. New (non-)members always have Moderation set to List default. This means their posts are governed by the applicable Settings -> Message Acceptance settings. Setting a user's Moderation to Default Processing means that users posts will not be held/rejected/discarded/accepted immediately based on "Default action to take when a (non-)member posts to the list", but additional checks will not be bypassed. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. > Are my deductions correct? And if so, could this be the explanation of > the issue detailed in this thread? Setting a user's Moderation to Default Processing (or Accept) would bypass the list defaults and could be the explanation of this issue. When the non-member owner first posts to the list that address becomes a non-member of the list. I.e. it is in the roster of known non-members of the list and that non-member record could have had its Moderation set to Accept or Default Processing at some point which would explain why the posts are accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

Mailman-users search results for query "Postorius"