Mailman-users search results for query "Postorius"

mailman-users@mailman3.org

3139 messages

Re: Postorius no connection to REST API

by Mark Sapiro

On 9/4/23 11:43, markus.laspeyres--- via Mailman-users wrote: > > But sudo systemctl restart mailman3 > Job for mailman3.service failed because the control process exited with error code. > See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details. And what do those say? -- 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: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Wikinaut

Hmmm, regarding POSTORIUS_TEMPLATE_BASE_URL , just as a remark, 'http://localhost/mailman3/', this was the installed default value. Regarding the django issue: I do not remember to have triggered an update or so when suddently the error popped up, I did the pip install -U after that. Do you have a recommendation for me, a hint, how to fix the problem without losing the database and settings of my mailing lists? It is so strange to see the error just right now (while only concentrating on the "template problem"); mailman3 worked for a long time.

1 year, 9 months

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

by Wikinaut

> Maybe you can make your life a little more bearable by abandoning the use of Debian packages and embracing the virtualenv.... I fully understand. Need to look up how to smoothly backup the mailman3 settings and list databases in order to make that move with losing stuff... (kinda "mailman3 backup all" and mailman3 restore all" :-)

1 year, 9 months

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

by Wikinaut

* correction: withOUT losing stuff...

1 year, 9 months

Re: Splitting hosts: mta&core vs postorius

by Stephen J. Turnbull

samuel.d.darwin(a)gmail.com writes: > The current implementation of [webservice] hostname is confusing > and difficult to work with. Is this a bug report/request for enhancement or a documentation patch?

1 year, 6 months

Re: Error -- postorius Un-handled exception

by Mark Sapiro

On 1/23/24 21:48, Mark wrote: > > And the Mailman log is a mystery to me, and no error is reported in the > Nginx log ... Is there any error and/or traceback reported in /opt/mailman/mm/var/logs/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark Sapiro wrote: > What's in var/logs/mailman.log? Good question! > 2024-04-10 12:42:08 [FALCON] [ERROR] GET /3.1/lists/new_test.domain.tld/arch ivers => Traceback (most recent call last): > ... > ModuleNotFoundError: No module named 'mailman_hyperkitty' That has me confused, as the footer says > Powered by HyperKitty version 1.3.9.

1 year, 3 months

Re: Error -- postorius Un-handled exception

by Mark Sapiro

On 4/10/24 12:52, admin(a)bclug.ca wrote: > >> 2024-04-10 12:42:08 [FALCON] [ERROR] GET /3.1/lists/new_test.domain.tld/arch > ivers => Traceback (most recent call last): >> ... >> ModuleNotFoundError: No module named 'mailman_hyperkitty' > > > That has me confused, as the footer says > >> Powered by HyperKitty version 1.3.9. mailman_hyperkitty is a separate package which is a shim between Mailman core and HyperKitty. In your venv or wherever Mailman is installed, you need ``` pip install mailman_hyperkitty ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark Sapiro wrote: > > ModuleNotFoundError: No module named 'mailman_hyperkitty' > > That has me confused, as the footer says > > Powered by HyperKitty version 1.3.9. > > mailman_hyperkitty is a separate package which is a shim between Mailman > core and HyperKitty. In your venv or wherever Mailman is installed, you need > pip install mailman_hyperkitty It should be already installed, as it shows in the footer? > (venv) mailman@mail:~$ pip install mailman_hyperkitty > Requirement already satisfied: mailman_hyperkitty in ./venv/lib/python3.10/site-pa ckages (1.2.1) > ... > (venv) mailman@mail:~$

1 year, 3 months

Re: Error -- postorius Un-handled exception

by Mark Sapiro

On April 10, 2024 1:15:34 PM PDT, admin(a)bclug.ca wrote: > >It should be already installed, as it shows in the footer? > > >> (venv) mailman@mail:~$ pip install mailman_hyperkitty >> Requirement already satisfied: mailman_hyperkitty in ./venv/lib/python3.10/site-pa >ckages (1.2.1) >> ... >> (venv) mailman@mail:~$ I suspect you are not starting the services with your venv active. What's in your mailman3.service and mailman3-web.service files? -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 3 months

Jump to page: