Search results for "Postorius" - Mailman-users

Re: Postorius: Show only own lists

by Simon Hanna

On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > Imagine an installation with 500+ mailing lists and almost as many local > admins that are supposed to maintain their own local lists with a few local > members. As site admin, I see all 500+ lists, but I was expecting *local* > admins to see only the lists they maintain. I have set all lists to > "advertised = False", so they are hidden from ordinary view. Is there a way > to show only relevant lists to local admins? Are we talking about Postorius or Hyperkitty? There is no way for users that do not have the django superuser permission, to see unadvertised lists in the Postorius list index. I just doublechecked the source. There is an issue about list filtering/search for the index page.

8 years, 8 months

Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 8:14 AM, Gelpi Andrea wrote: > > I search internet for a while and I discovered that using > FILTER_VHOST = True > seems to solve the problem. > >>From posotrius config page: > > FILTER_VHOST > Filter the list of available lists in Postorius and Hyperkitty > depending on the domain they are being currently served from. Mailman 3 > supports multiple domains in a single installation. > > But it doesn't work. I got err 500 form apache. FILTER_VHOST is currently broken unless each domain has the same value for the web and email domains. See the thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > Were can I find an explanation or a how to configure the system to have > 2 webserver with different domains working on the some server as it was > with mailman 2? If each domain has the same value for the web and email hosts, FILTER_VHOST will work. Currently though if you have domains like web host = lists.example.com and email host = example.com, FILTER_VHOST is broken. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Mark Sapiro writes: > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, That's true from "outside", but there are internal links as well. For example, in Postorius top page, the link to HyperKitty is .../archives. I guess it's a good idea to grep the templates to see which URLS are used. > > Now my question is about what could be adding the /mailman3. Is it possible > > that I installed something out of the ordinary? Besides mod_wsgi as Mark suggests and the uwsgi configuration, the only thing I can think of is an Apache rewrite rule. It's not in the Postorius and HyperKitty templates. Steve

3 years, 8 months

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

by 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? When you say root account, do you mean the Django superuser account? Also have you made sure all of the permissions are owned by the mailman user in /opt/mailman? -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years

Different Mail Domain Cause Key Error

by Brian Carpenter

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com) I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

6 years, 5 months

Postorius performance with over 1000 pending users

by Nick W

I've got a couple things I need help with: The Symptom and The Problem. The Symptom: Postorius has gotten quite slow to load, taking more than 30s to load the Subscription Requests tab. Having zero pending subscription requests (I'm on v1.2.5), I started investigating unconfirmed subscriptions. I followed the commands from here[1] and got this: mailman shell -l your.list.id util = getUtility(IPendings) print(len(list(util.find(mlist=m,pend_type='subscription')))) 1816 Wow, 1816 pending subscription requests. I can say for certain that my list is not popular so these requests must have been submitted by bots. Let's get there in The Problem. How can I "purge" this list? I'm willing to assume that none of these requests are valid and would reject all unconfirmed user requests. The Problem: How might this activity be happening? Running cat /opt/mailman/core/var/logs/mailman.log | grep POST returns a lot of 202 and 409 responses for `POST /3.1/members`. Could it be that these requests are being submitted through Postorius? I'd assume there would be some sort of honeypot input to prevent abuse. I'll continue investigating and follow up with any insight I can on the cause of The Problem. Thanks, Nick [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>

7 years, 3 months

Re: Message-Footer after migrating to Mailman3

by Abhilash Raj

> On Jul 9, 2021, at 9:15 AM, christopher.claus(a)tgcamberg1848.de wrote: > > Mark Sapiro wrote: >>> ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. >>> WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer >>> It appears you created the new template with Postorius, but there is an >> issue for Postorius templates. Possibly your Django setting for >> POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. >>> Obviously I have a problem with the hostname. I set >>> [code] >>> POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 >>> [/code] >>> where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost >>> [code] >>> wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... >>> [/code] >>> will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? >>> If that works, yes. > > Hi Mark, > > thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.ex…) > But if I try to send an email I got the following error: You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? If you want to verify, you want to exec into the Core’s container (`docker exec -it mailman-core bash`) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence `http://mailman-web:8000` works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). -- thanks, Abhilash Raj (maxking)

5 years, 1 month

Re: FILTER_VHOST fix - was: Postorius & multi domain

by jdanitxu＠gmail.com

Hi, we are writing from the NGO Engineering Without Borders - Spain. After having migrated from mailman2 to mailman3 in a server with Debian 11, our domains are like these: https://listas.isf.es/mailman3/ https://listas.andalucia.isf.es/mailman3/ https://listas.aragon.isf.es/mailman3/ ... I have set FILTER_VHOST = True and restarted postorius (systemctl restart mailman3-web), but when we enter in every URL, we see all the lists. Any hint to search? Thanks a lot in advance! P.S: apart from this conversation, I suggest to include in documentation related to migrations the fact that is important to have 'charset': 'utf8mb4' if MariaDB/MySQL is used, in order not to get migration errors doubt to encodings. We had 75 GB of mbox messages and some of them have had trouble doubt to not setting it before.

4 years, 8 months

error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Guillermo Hernandez (Oldno7)

I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I've just upgrade mailman 3 installation following Mr. Sapiro advice: > did a > > pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient > mailman-hyperkitty postorius > > I did a "python3 manage.py migrate" after, too. > > And all seemed to run well. > > All the lists showed in postorius via web, but when I try to accesss > into one of them the browser shows an error. > > In the log you can see: > > *-*-*-*-*-*-* > > Traceback (most recent call last): > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ > return self._get(name) > File > "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", > line 86, in _get > raise KeyError(key) > KeyError: 'get_requests_count' > > ... (And after all the traceback lines) > > AttributeError: 'MailingList' object has no attribute > 'get_requests_count' > > *-*-*-*-*-*-*-* > > The lists seem to be distributing messeages well.. but I cannot acces > via web administration (django/postorius) > > Can anyone point me in the right direction to solve this, please? > > _______________________________________________ > 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/ >

5 years, 7 months

Re: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/12/21 8:38 AM, Tibor Molnar wrote: > Hello, > > I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 > I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. > The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated. These are all HyperKitty pages, not Postorius. Did you run all the post-upgrade tasks mentioned at <https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade> after upgrading? Also, it is possible, but not the likely cause of this, that there is an incompatibility between the latest hyperkitty and django-mailman3 in PyPI. See <https://gitlab.com/mailman/django-mailman3/-/issues/48>. You could try ``` pip install -U git+https://gitlab.com/mailman/hyperkitty.git ``` and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Mailman-users search results for query "Postorius"