Search results for "Postorius" - Mailman-users

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: > I'm trying to set up mailman3 on two hosts, one of which runs core + > exim, the other runs postorius (&possibly hyperkitty). > > I have I think got core set up correctly, and postorius is sort of > usable, but anything in the web ui that talks to core ends up with a > white screen. > > I think what is happening is a postorius URL ends up with the core (or > perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? > I've checked the settings and I don't think I have misconfigured > postorius. Is it possible that the bad url is being passed from core to > postorius in some way and reused without changing the host? > > In the config at present, both hosts are visible to the browser, and > each host can communicate with the other. > > Any ideas on how to pin down the problem better? Do you see REST requests from the Postorius machine in core's mailman.log and access.log? -- 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

problem with postorius initial setup

by Stephen J. Turnbull

John Covici writes: > Hi. I am trying to setup postorius, but I have run into a problem. I > am using the example project, except I am using postgresql instead of > sqlite3. I ran python manage.py migrate which was successful. > > On running the development server I get: > Exception in thread django-main-thread: > Traceback (most recent call last): > File > "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", > line 20, in import_string > return getattr(module, class_name) > AttributeError: module 'postorius.middleware' has no attribute > 'APICountingMiddleware' This appears to be another version mismatch. The APICountingMiddleware appears to be a debugging or development instrumentation tool. It was added on 2021-02-28, so it's very recent. Somehow your Postorius settings.py is newer than your Postorius middleware.py. I would guess you have checked out or pip'ed a very recent version of Postorius but the example_project is picking up an older version, possibly from the Gentoo package. Why that could happen depends on whether you've set up a venv for the up-to-date Postorius, whether it's active, and so on. Steve

4 years, 11 months

Re: problem with postorius initial setup

by Abhilash Raj

-- thanks, Abhilash Raj (maxking) > On Mar 16, 2021, at 11:35 AM, John Covici <covici(a)ccs.covici.com> wrote: > > On Tue, 16 Mar 2021 12:14:36 -0400, > Stephen J. Turnbull wrote: >> >> John Covici writes: >> >>> Hi. I am trying to setup postorius, but I have run into a problem. I >>> am using the example project, except I am using postgresql instead of >>> sqlite3. I ran python manage.py migrate which was successful. >>> >>> On running the development server I get: >>> Exception in thread django-main-thread: >>> Traceback (most recent call last): >>> File >>> "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", >>> line 20, in import_string >>> return getattr(module, class_name) >>> AttributeError: module 'postorius.middleware' has no attribute >>> 'APICountingMiddleware' >> >> This appears to be another version mismatch. The >> APICountingMiddleware appears to be a debugging or development >> instrumentation tool. It was added on 2021-02-28, so it's very >> recent. Somehow your Postorius settings.py is newer than your >> Postorius middleware.py. I would guess you have checked out or pip'ed >> a very recent version of Postorius but the example_project is picking >> up an older version, possibly from the Gentoo package. Why that could >> happen depends on whether you've set up a venv for the up-to-date >> Postorius, whether it's active, and so on. > > I think I know what is happening, but not how to fix. The > example_project which the docs told me to get is from the postorius > git which is, of course, recent, whereas the postorius I have from the > gentoo package is 1.3.3, which is not that old, but maybe not up to > the git version. Should I be using the git version? You want to follow this guide[1] for installing from pip. It covers both Postorius and Hyperkitty. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… I am assuming you saw it in this doc [2] to use the example_project. That is very specific to development installations. I will update the document to make it clearer and point to [1] for any production setup. [2]: https://docs.mailman3.org/projects/postorius/en/latest/setup.html#setup-you… > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com > _______________________________________________ > 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, 11 months

Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Wikinaut

After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one) POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' the web access via Postorius is not working any more and throws "Error 500" My logfile /var/log/mailman3/web/mailman-web.log shows now File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 116, in populate app_config.import_models() File "/usr/local/lib/python3.9/dist-packages/django/apps/config.py", line 269, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 790, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/django_q/models.py", line 12, in <module> from django_q.signing import SignedPackage File "/usr/lib/python3/dist-packages/django_q/signing.py", line 7, in <module> from django_q import core_signing as signing File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 9, in <module> from django.utils.encoding import force_bytes, force_str, force_text ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) I already run pip install -U postorius to update that (looks okay to me): Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) Collecting postorius Using cached postorius-1.3.8-py3-none-any.whl Downloading postorius-1.3.7.tar.gz (3.2 MB) Requirement already satisfied: django-mailman3>=1.3.8 in /usr/local/lib/python3.9/dist-packages (from postorius) (1.3.9) Requirement already satisfied: readme-renderer[md] in /usr/lib/python3/dist-packages (from postorius) (24.0) Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) Requirement already satisfied: mailmanclient>=3.3.3 in /usr/local/lib/python3.9/dist-packages (from postorius) (3.3.5) Requirement already satisfied: sqlparse>=0.2.2 in /usr/lib/python3/dist-packages (from django<4.2,>=3.2->postorius) (0.4.1) Requirement already satisfied: asgiref<4,>=3.5.2 in /usr/local/lib/python3.9/dist-packages (from django<4.2,>=3.2->postorius) (3.7.2) Requirement already satisfied: typing-extensions>=4 in /usr/local/lib/python3.9/dist-packages (from asgiref<4,>=3.5.2->django<4.2,>=3.2->postorius) (4.6.3) Requirement already satisfied: django-allauth in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (0.44.0) Requirement already satisfied: pytz in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (2021.1) Requirement already satisfied: django-gravatar2>=1.0.6 in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (1.4.4) Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from mailmanclient>=3.3.3->postorius) (2.25.1) Requirement already satisfied: cmarkgfm>=0.2.0 in /usr/lib/python3/dist-packages (from readme-renderer[md]->postorius) (0.4.2) dpkg -l | grep django ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework ii python3-django-allauth 0.44.0+ds-1+deb11u1 all Django app for local and social authentication (Python 3 version) ii python3-django-appconf 1.0.3-1 all helper class handling configuration defaults of apps - Python 3.x ii python3-django-compressor 2.4-2 all Compresses linked, inline JS or CSS into single cached files - Python 3.x ii python3-django-extensions 3.0.3-3 all Useful extensions for Django projects (Python 3 version) ii python3-django-filters 2.4.0-1 all filter Django QuerySets based on user selections ii python3-django-gravatar2 1.4.4-2 all Python3 library that provides essential Gravatar support ii python3-django-guardian 2.0.0-2 all per object permissions of django for Python3 ii python3-django-haystack 3.0-1 all modular search for Django (Python version) ii python3-django-hyperkitty 1.3.4-4 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-picklefield 3.0.1-1 all Pickled object field for Django (Python3 version) ii python3-django-postorius 1.3.4-2+deb11u1 all Web user interface to access GNU Mailman3 ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version) ii python3-djangorestframework 3.12.1-1 all Web APIs for Django, made easy for Python3 debian 11 (bullseye) Looks to be a problem between django 4 and /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py ? Please can anybody help?

2 years, 5 months

Re: Postorius 1.1.2 security release

by Marvin Gülker

Hi, Am 27. December 2017 um 23:16 Uhr -0800 schrieb Abhilash Raj <maxking(a)asynchronous.in>: > Python 2.7 is the only supported Python version for this release. All versions > of Django <=1.11 is supported. I see the below error when I try to upgrade postorius. Given the statement above, I assume it's a problem with Django then -- I've got no Python experience after all. So, what's the correct way to upgrade postorius if just using `$ pip install --upgrade' doesn't work? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (env2) mailman@alexandria:~$ pip install --upgrade postorius Collecting postorius Downloading postorius-1.1.2.tar.gz (383kB) 100% |████████████████████████████████| 389kB 2.1MB/s Collecting Django>=1.8 (from postorius) Downloading Django-2.0.tar.gz (8.0MB) 100% |████████████████████████████████| 8.0MB 137kB/s Complete output from command python setup.py egg_info: Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-build-_z8tGq/Django/setup.py", line 32, in <module> version = __import__('django').get_version() File "django/__init__.py", line 1, in <module> from django.utils.version import get_version File "django/utils/version.py", line 61, in <module> @functools.lru_cache() AttributeError: 'module' object has no attribute 'lru_cache' ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-_z8tGq/Django/ (env2) mailman@alexandria:~$ python --version Python 2.7.13 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Greetings Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 2 months

Re: Core, Hyperkitty and Postorius releases

by Torge Riedel

Am 03.02.21 um 02:59 schrieb Abhilash Raj: > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Dear MM3 releasers, after successful update to latest versions I realized that Mailman Core change log links are stable (I requested this some time ago and it was changed - thanks for that), but Postorius and Hyperkitty change logs do not have stable header ids. Can this be changed too? It makes it easier for me (and hopefully for others) when communicating changes to the users. At the moment they see the upcoming changes for Postorius first, which always introduces confusion for some of them. Thanks in advance and kind regards Torge

4 years, 10 months

mailman_web/urls.py changes in Postorius 1.3.10

by Lieuallen, Thomas Otis

The latest release of Postorius includes these lines in mailman_web/urls.py: # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), It appears that these paths override the originals (/mailman3 & /archive). I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? Thank you Tom Lieuallen

2 years, 3 months

Re: Time Zone Issue in Postorius

by Mark Sapiro

On 2/4/22 09:48, Andy Summers wrote: > Hello, > > I'm encountering an error that sounds similar to this previous thread: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I've tried setting my TIME_ZONE to 'UTC' in my settings.py and > settings_local.py files (and restarting Mailman), but when I check the > datetime for a held message in Postorius, the datetime seems to be > pushed +8 hours unexpectedly. > > My Postorius account time zone is set to "US/Pacific". The appropriate setting for Django is always `TIME_ZONE = 'UTC'`because the time passed from Mailman core is a naive datetime.datetime object and is actually UTC. This should then display the time in your account timezone since Postorius 1.3.4. See https://gitlab.com/mailman/postorius/-/merge_requests/531 If this isn't working in Postorius >=1.3.4, it's a Django issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Mailman Core 3.1.1 and Postorius 1.1.1 released

by Abhilash Raj

Hello Everyone, I am pleased to announce the release of Mailman Core 3.1.1 and Postorius 1.1.1. Python 2.7 is the only supported version for Postorius 1.1.1 and Python 3.5-3.6 are supported for Mailman Core 3.1.1. Both of these are bugfix releases and include some improvements. For a full list of changes, please see [1] for Core and [2] for Postorius. [1]: http://mailman.rtfd.io/en/release-3.1/src/mailman/docs/NEWS.html [2]: http://docs.mailman3.org/projects/postorius/en/latest/news.html For more information about GNU Mailman, please see our wesbite at one of the following: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ Documentation for Mailman 3 is available at: http://docs.mailman3.org/en/latest/ Both of these can be downloaded from PyPI. https://pypi.org/project/mailman/ https://pypi.org/project/postorius/ thanks, Abhilash Raj

8 years, 3 months

Re: Postorius 1.1.2 security release

by Simon Hanna

On 12/29/2017 08:57 PM, Marvin Gülker wrote: > Hi, > > Am 27. December 2017 um 23:16 Uhr -0800 schrieb Abhilash Raj <maxking(a)asynchronous.in>: >> Python 2.7 is the only supported Python version for this release. All versions >> of Django <=1.11 is supported. > I see the below error when I try to upgrade postorius. Given the > statement above, I assume it's a problem with Django then -- I've got no > Python experience after all. So, what's the correct way to upgrade > postorius if just using `$ pip install --upgrade' doesn't work? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > (env2) mailman@alexandria:~$ pip install --upgrade postorius > Collecting postorius > Downloading postorius-1.1.2.tar.gz (383kB) > 100% |████████████████████████████████| 389kB 2.1MB/s > Collecting Django>=1.8 (from postorius) > Downloading Django-2.0.tar.gz (8.0MB) > 100% |████████████████████████████████| 8.0MB 137kB/s > Complete output from command python setup.py egg_info: > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "/tmp/pip-build-_z8tGq/Django/setup.py", line 32, in <module> > version = __import__('django').get_version() > File "django/__init__.py", line 1, in <module> > from django.utils.version import get_version > File "django/utils/version.py", line 61, in <module> > @functools.lru_cache() > AttributeError: 'module' object has no attribute 'lru_cache' The issue is that django 2.0 doesn't support python3 anymore.

8 years, 2 months

Mailman-users search results for query "Postorius"