Search results for "Postorius" - Mailman-users

Re: only show mail domains from web host on web-host-url

by Jens Günther

Just checked again and saw: - in the setup it works perfectly in Hyperkitty, that's nice - for the first web host I have 2 mail domains registered, so it also matches (unfortunately) with what you said :-( Anyway, I dceleted one of it, still both lists are shown on either web host, so it's generally not working. If I can do something on this issue, please advise me. Thanks. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host.

4 years, 8 months

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 9:29 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > >> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: >> >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 >> [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ >> (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts >> [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ >> TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives >> [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ >> TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) >> >> The proxy pass config is >> <IfModule mod_proxy_uwsgi.c> >> ProxyPass /mailman3/favicon.ico ! >> ProxyPass /mailman3/static ! >> Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" >> ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" >> ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" >> ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" >> ProxyPass "/django" "http://127.0.0.1:8000/django" >> ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" >> ProxyPass "/archives" "http://127.0.0.1:8000/archives" >> </IfModule> > > There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. Also, replace, /django with /admin. > You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Do, either one of those listed above and `/admin` work for you? -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 11:08, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > El 26/12/22 a las 19:19, Mark Sapiro escribió: >> On 12/26/22 07:42, Odhiambo Washington wrote: >> >>> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >>> >>> Does your https://site.name/user-profile/ work? >> >> Again, Guillermo is using uWSGI, not Apache mod_wsgi > > Well... now I am not sure, you know I've been confused before about that. I was looking at what you posted at https://forums.freebsd.org/threads/mailman-3.61050/#post-488128. I focused on the part beginning with - initiated the uwsgi with a /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & Which is running uwsgi. However I overlooked the mod_wsgi stuff. > In my httpd.conf I have: > > ############## > > LoadModule wsgi_module > "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" > WSGIPythonHome "/usr/local" > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 > user=mailman3 group=mailman > WSGIProcessGroup hyperkitty > ############### This is all mod_wsgi. > And in then end of my vhost definition file there is this line: > > Include "/usr/local/mailman3/apache24.uwsgi.conf" > > In that file I have: > > ######### begin of apache24.uwsgi.conf > > Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman3/static > ######### > # for hyperkitty > Alias /static/admin /usr/local/mailman3/static/admin > Alias /static/CACHE /usr/local/mailman3/static/CACHE > Alias /static/django_extensions > /usr/local/mailman3/static/django_extensions > Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty > Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty > Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 > Alias /static/rest_framework /usr/local/mailman3/static/rest_framework > # for postorius > Alias /static/postorius /usr/local/mailman3/static/postorius > Alias /static/archives /usr/local/mailman3/static/postorius > ##### All the above between `#########` and `#####` is redundant as you already have Alias /static /usr/local/mailman3/static which will alias any /static/xxx to /usr/local/mailman3/static/xxx > ###ErrorLog /var/log/httpd/hyperkitty_error.log > ###CustomLog /var/log/httpd/hyperkitty_access.log combined > > <Directory "/usr/local/mailman3/static"> > Require all granted > </Directory> > #### esto va en el httpd.conf > ##WSGIDaemonProcess hyperkitty threads=25 > python-path=/usr/local/mailman3 user=mailman group=mailman > ## esta es la de Sapiro > #WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 > ####user=mailman group=mailman > ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 > ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > > #### agregado el 08/07/22 > WSGIPassAuthorization On > #### > > WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py > process-group=hyperkitty And this is also mod_wsgi. ... > I don't want to put more noise in the list. But I'm confused because I > always updated via pip the apache mod_wsgi thinking is was needed for my > configuration. If it is not, I will stop updating it. Based on the above you ARE using Apache mod_wsgi and if you are still also running uwsgi as /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & that is unnecessary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: django fake users

by Andrew Hodgson

Stephen J. Turnbull wrote: >Andrew Hodgson writes: > > >Require moderator approval for subscribing. > > I don't think this would help the issue. What I am seeing here is > users signing up through Postorius using the sign up option which > then creates an account in Django (but not Mailman). >Ah, so "fake" == "account in Django but no user in Mailman"? Yes. >I don't have time to look at it, so take this with a grain of salt, but I don't think they are passing the email confirmation. If they were, they would show up in Mailman. Actually I did confirm the same to this list later on, the accounts are indeed not passing email confirmation. >I think this would be simple enough to deal with (not trivial, so I'm not making any promises except to try adding it to the GSoC ideas page >-- that should be enough to clarify whether there are any "annoyance to 'real' users" issues, and we move forward from there if there aren't). Basically, Postorius should notify Mailman that there is a >*pending* user in Django, and if there's no confirmation by a deadline, remove that user. This requires a bunch of infrastructure like a table of "pending" users, callbacks for the deletion, etc, but I don't see why it would be conceptually difficult. (This combination is why I think it would be a good GSoC task) Sure. I would rather go this route rather than use captchas at this stage, though right now my Cron job running once a week is sufficient. Thanks. Andrew.

4 years, 10 months

Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Alan So writes: > However, some of our departmental staff sometimes forget to check > the box "Pre Verified" when they refresh (actually delete all and > subscribe all) list of members during term's start. [...] > Is this possible to add default setting of Pre Verified during > mass-subscription (for example settings.py) such that we can help > them a bit? I don't know if there's a way to do this in settings.py, but I suspect not. Maybe Mark knows a way. However, you can find .../site-packages/postorius/forms/list_forms.py (not sure exactly where that is in your instance but I guess you probably do), and find this code (AFAICT this is the unique instance of 'Pre Verified' in the whole Postorius code base) in that file: pre_verified = forms.BooleanField( label=_('Pre Verified'), initial=False, required=False, help_text=_( 'If checked, users will not have to verify that their ' 'email address is valid.'), widget=forms.CheckboxInput() ) Then just edit the line initial=False, to initial=True, Note that this will get overwritten if you upgrade (or reinstall) Postorius, and you'll have to do it again. But it will save you a ton of grief until that happens. Also note that if there *is* a way to do this in settings.py, it is *safe* to do that later without reverting the change to list_forms.py, and the settings.py setting will continue to work after any upgrade or reinstall. So you can patch list_forms.py now without worrying it will get you into trouble later. Steve

2 years, 11 months

[Django] ERROR (EXTERNAL IP): Service Unavailable

by dancab＠caltech.edu

I've imported a list from Mailman2 and had the owner send a message for testing purposes. His message are moderated per the list configuration. The message is delivered to Mailman3 and shows that it's being held. However if we attempt to view the message in Postorius web UI then an error is thrown. In the web interface the error is simply "Mailman REST API not available. Please start Mailman core." But Mailman Core is running and we can do other functions just fine. Our superuser account receives a much more detailed message with the subject below. [Django] ERROR (EXTERNAL IP): Service Unavailable: /postorius/lists/cpa-announcement.caltech.edu/held_messages Does "Service Unavailable" mean I'm missing something in the configuration? Thanks for your help. ---- Dan Caballero

4 years, 9 months

Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I think I found the bug; I have posted a comment to the issue mentioned by Mark https://gitlab.com/mailman/postorius/issues/58 Regards Claus Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: > Oh well. > > Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>> >>> Seemingly, at some point in the deep dungeons of the source code the >>> "Acceptable aliases" Text-Box is not interpreted correctly. >>> >>> Specifically, at the start it contains the string >>> >>> [] >> >> >> See <https://gitlab.com/mailman/postorius/issues/58>. > > there they talk about fancy "uni-code thinks" (email addresses?) where > the task is to convert a new-line separated text-field into an array. Oops. > > Kind thanks anyway. > >> >> In order to set things on this page, you need to clear the Acceptable >> aliases box before submitting changes. You can't actually set Acceptable >> aliases via Postorius until this is fixed. > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. > > Thanks > > Claus > > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 3 months

Re: Unable to update templates

by Mark Sapiro

On 5/27/25 18:54, Mark wrote: > > However when I update the template, the databases are updated correctly > but the Welcome message is still sent with the old template content. > > mailman.templates > mailmanweb.postorius_emailtemplate > > Additionally, if I delete the template and create a new one the old > content still gets sent. > > I cannot find where this content is written or is being cached. The content is stored in the mailmanweb.postorius_emailtemplate table. As far as Mailman core and Postorius are concerned, that's the only place. I'm guessing, but my guess is it's cached in your wsgi server. I.e., upon initial creation an entry is made in the mailman.template table with a uri like https://example.com/mailman3/api/templates/list/list.example.com/list:user:… and when Mailman core wants the template, it gets that uri which I'm guessing is then cached in the wsgi server. Then, if the content is changed, the GET returns the old cached value instead of getting the new value from Postorius. If the template is deleted, the mailman.template table entry is deleted and at that point Mailman core will get the template from the file system following it's normal search rules, but if the template is recreated in Postorius, a new table entry is made with the same uri which may still get a cached template from the wsgi server. If this is correct, restarting mailman-web or whatever controls the wsgi server should fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ > TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ > TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > > The proxy pass config is > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/django" "http://127.0.0.1:8000/django" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > </IfModule> There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Top level URL patterns are basically listed here[1], but it depends on where did you install from and what the url patterns are. [1]: https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py#L25 > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Error: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class

by Torge Riedel

Dears, I just upgraded my Server from Ubuntu 22.04 to 24.04 and I get the following error when accessing the web page. Django is 5.0.10 Postorius is 1.3.13 Any help is welcome. Thank you and kind regards Torge Internal Server Error:/mailman3/lists/ ImportError at/mailman3/lists/ Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Request Method: GET Request URL:https://lists.lsv-pinneberg.de/mailman3/lists/ Django Version: 5.0.10 Python Executable: /usr/bin/uwsgi-core Python Version: 3.12.3 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/opt/mailman/web/venv/lib/python3.12/site-packages'] Server time: Sun, 22 Dec 2024 11:05:00 +0100 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', 'allauth.account.middleware.AccountMiddleware') Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 30, in import_string return cached_import(module_path, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 16, in cached_import return getattr(module, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ The above exception (module 'django.contrib.sessions.serializers' has no attribute 'PickleSerializer') was the direct cause of the following exception: File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/deprecation.py", line 133, in __call__ response = self.process_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/middleware.py", line 20, in process_request request.session = self.SessionStore(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/db.py", line 16, in __init__ super().__init__(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/base.py", line 47, in __init__ self.serializer = import_string(settings.SESSION_SERIALIZER) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 32, in import_string raise ImportError( ^^^^^^^^^^ Exception Type: ImportError at/mailman3/lists/ Exception Value: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Raised during: postorius.views.list.list_index

11 months, 1 week

Mailman-users search results for query "Postorius"