Search results for "Postorius" - Mailman-users

Re: Welcome message template errors

by Mark Sapiro

On 4/21/24 19:15, Mark wrote: > > And the site-owner receives an email with ... > > ==== > Internal Server Error: /mailman3/lists/ > DoesNotExist at /mailman3/lists/ > Site matching query does not exist. > Request Method: GET > Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/ The above means you have to add <REDACTED-PUBLIC-IPv4-ADDRESS> to the list of ALLOWED_HOSTS in your Django settings, but see below. > Django Version: 4.2.11 > Python Executable: /opt/mailman/venv/bin/python3 > Python Version: 3.11.2 > ... etc ... > === > > Regarding the second line in the email - my thinking is that it should > be looking in "/opt/mailman/mm/var/lists" and not "/mailman3/lists/". It's talking about the path in the URL, not a path in the file system. > The error doesn't occur if the is no custom "Welcome message" template - > ie. the user is sent the default welcome message. I think you must be setting the custom template via Postorius and your Django setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. It should be set to the scheme and host you use to access Postorius. I.e, if you normally access Postorius via something like https://example.com/mailman3 set POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' It is probably now set as POSTORIUS_TEMPLATE_BASE_URL = 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > The localhost address is coming in via the hosts file, which is a > relatively standard practice IMO. I could change it, but then perhaps > other things would not work. I would prefer to be able to specify what I > need. There are also things like systemd-resolvd which will do the > localhost-substitution for you even if /etc/hosts doesn't. I have done further testing. See my comment at <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. You need to set hostname: in mailman.cfg to the actual external IP address of the Mailman host machine or to a name which resolves to that IP both internally and externally, and also set that host name/IP in the MAILMAN_REST_API_URL setting on the Postorius machine. > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. Remove that patch and do the above. > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Make the above changes and see if that solves this. If not, let us know and we'll try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

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

by Jens Günther

Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… How could I check, that the setting is used!? But maybe some additional information: - I use the Debian installation on a stable buster, so mailman is version 3.2.1 - I use apache2 as my web-server and use the given alias-conf-file - Python is version 3.7.3 - Postorius is Version 1.2.4 - HyperKitty is version 1.2.2 -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains What do I miss? Or where to investigate? Thank you in advance, best regards. By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Am 18.03.21 um 21:52 schrieb Mark Sapiro: > On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? > > Set FILTER_VHOST = True in your settings_local.py or where ever you put > your site Django settings. > >

5 years

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/23/20 12:11 PM, Gelpi Andrea wrote: > > > I can confirm that the fix works. > > Thank You so much. Thank you for testing and reporting. Note I have just made one minor change to the fix. Where I had in the added code > if (MailDomain.objects.get( > mail_domain=domain.mail_host).site.name == web_host): I now have > if (MailDomain.objects.get( > mail_domain=domain.mail_host).site.domain == web_host): The issue is site.name is the domain's display name whereas the domain name is site.domain. This only matters if you have given the site a display name different from the domain name in Django. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: Postorius upgrade issue

by Joel Lord

So I tried to do this after upgrading, fortunately only from 1 point release back, and I get "ModuleNotFoundError: No module named 'paintstore'" from the collectstatic. Haven't tried to get past that point, and haven't really had the time to chase this down myself. It seems like that's referring to a requirement from several versions back, but this venv was built clean only 2 months ago so it strikes me as odd. On 2/8/2021 6:18 PM, Mark Sapiro wrote: > I neglected to mention `migrate`. All 4 Django management commands, `collectstatic`, > `compress`, `compilemessages` and `migrate` should be run after any upgrade. > _______________________________________________ > 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/ > -- Joel Lord

5 years, 1 month

Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Flo

Hi, I have setup in Debian Trixie mailman3-full and came that far, that I have created a mailing list. I can sent emails to the members. However when I send from an email which is non-member the message is held. If I want to accept this message as list admin, I get: `An error occurred while processing your request.` And I get an email: `Internal Server Error: /mailman3/postorius/.../held_messages TemplateSyntaxError at /postorius/lists/.../held_messages 'humanize' is not a registered tag library. Must be one of: account admin_list admin_modify admin_urls allauth bootstrap_tags cache compress d_gravatar date_helpers debugger_tags decorate gravatar highlight highlighting hk_generic hk_haystack i18n indent_text l10n log markdown membership_helpers more_like_this nav_helpers p_gravatar pagination postorius_helpers rest_framework socialaccount static syntax_color tz widont Request Method: GET Request URL: https://.../mailman3/postorius/lists/.../held_messages Django Version: 4.2.23 Python Executable: /usr/bin/uwsgi-core Python Version: 3.13.5 Python Path: ['.', '', '/usr/lib/python313.zip', '/usr/lib/python3.13', '/usr/lib/python3.13/lib-dynload', '/usr/local/lib/python3.13/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3/dist-packages/setuptools/_vendor'] . . .` humanize is in the INSTALLED_APPS section in /usr/share/mailman3-web/settings.py. In this file I I configured Django. However it's not in the Python path as written in the error email above. So maybe I have to find a different settings file. Can anyone advise me where I can find the error I have in my configuration? Thanks in advance. Flo

6 months, 3 weeks

Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 18:08, Abhilash Raj wrote: > > On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I restarted de server and the error changed. Now the log shows >> "KeyError: 'subscription_mode'": > Did you also restart Mailman Core after the upgrade? Yes, indeed: I stopped mailman core and all the processes related. Did the upgrades. Started all again. Find the errors in the web user interface. Stopped all again. Looked for errors in the log. Restarted the complete server. Found the second error that this second mail is about to. It happens when, in the main page that shows all the lists you click to see one of them. It seems to me that it has been database structure changes in django that the upgrade is not aware... but it's a very long shot from my side. I'm using sqlite as django database and mysql for mailman. > >> 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/ >>> >> _______________________________________________ >> 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, 1 month

Re: Apache shows No Lists

by Mark Sapiro

On 5/21/23 15:15, ceo(a)sartrack.nz wrote: > Running Debian 11. > > I have 6 mailing lists, but Apache2 says there are no lists. > I have not been able to set up Postorius because nowhere is any information on *where* the configuration file is supposed to be located. If Postorius is not running, what is Apache looking at? > I have found an example in > /usr/share/doc/python3-django-hyperkitty/examples/settings.py > > But I don't know if this example is the right one, and I have no idea where the final file should go... Please follow the doc at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. This is our current recommendation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

High Server Load problem

by Brian Carpenter

For about a week now, I am seeing very high server loads and it seems to have something to do with the following process hanging: uwsgi --ini /opt/mailman-web/uwsgi.ini I am using the docker version of Mailman. When this process hangs, the server load just goes sky high and both Postorius and Hyperkitty no longer responds. I don't have very many sites on this server and I am running about 30 lists. I really need some assistance here as this needs to be fixed. I am seeing nothing in the logs that is explaining why this process is hanging and why the server load goes through the roof. Running docker-compose restart mailman-web kills the hanged process and the server load goes down. Postorius and Hyperkitty starts responding again. This seems to happen once a day. Brian

6 years, 4 months

Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/3/22 04:53, mhazan(a)mandint.org wrote: > > working on that plugin, i have found where to inserts the various > setting, however it's not clear what types and possibles value are > excepted for each ? ie "advertised" is bool True/false, but what about > "default_member_action" ? i've tried hold 'hold' "hold" all throw error > when trying to apply the style. from mailman.interfaces.action import Action mlist.default_member_action = Action.hold > i cannot find the types in the > documentation and all the other non bool settings. Look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for an example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Mailman-users search results for query "Postorius"