Search results for "Postorius" - Mailman-users

Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by Mark Sapiro

On 7/7/22 11:10 AM, David Newman wrote: > On 7/7/22 10:25 AM, Mark Sapiro wrote: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > uwsgi > > and it downgraded Django back to 3.0.14. Because mailman-web 0.0.5 has in its setup.cfg ``` install_requires = Django<3.1 ``` try ``` pip install -U git+https://gitlab.com/mailman/mailman-web.git ``` to get the latest mailman-web whose Django requirement is ``` install_requires = django >=2.2, !=3.0, <4 ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

mailman 3.x upgrade and downgrade

by skooperit＠gmail.com

Hi all, I have a few contradictory questions. 1. How to upgrade the 3.x version? 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? 3. If so, what would be the best way to do that? My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: django-mailman3 1.3.5 mailman 3.3.2 mailman-hyperkitty 1.1.0 mailman-web 0.0.3 mailmanclient 3.3.2 postorius 1.3.3 We have ~200 lists with more than a decade of history. thanks -- Carlos Souza

3 years, 1 month

Re: Can't Start Mailman3 Core on Fresh Install

by Mail Person

Ok, I've got more progress. The initial server error was fixed by re-running the configurations for mailman3 and mailman3-web. I believe an error occurred because I changed the passwords for the mailman3 users and only updated them in the cfg files in /etc/mailman3 and they must be stored somewhere else. Now the web interface shows as working, but it is showing "example.com" and when I go to sign-in with the postorius super user, I get a server error.

3 years

Re: Can't Start Mailman3 Core on Fresh Install

by Mark Sapiro

On 7/21/22 10:59, Mail Person wrote: > Now the web interface shows as working, but it is showing "example.com" and when I go to sign-in with the postorius super user, I get a server error. What's in your Django log? What is your setting for `SITE_ID` in your Django settings. This determines which Django `sites` table entry is displayed. See https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h…. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: User display name entry field input ignored

by Mark Sapiro

On 7/27/22 05:11, Christian via Mailman-users wrote: > Okay. What if I want to change the name from "None" to "firstname lastname" > ? How can that be accomplished please? In current Postorius (>=1.3.6) there is a `Users` button at the top of the screen. Click that, find the user you want to change and click `Manage` and you can update the display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/15/22 06:53, Odhiambo Washington wrote: > > That is exactly what I have in my mailman.cfg > > Installing Postfix suppresses that message though. I installed Postfix and > then disabled it. > Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman core than the one reading that mailman.cfg and the one Postorius is talking to. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/15/22 7:28 AM, Odhiambo Washington wrote: > On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman >> core than the one reading that mailman.cfg and the one Postorius is >> talking to. >> > > How can I track the one it's talking to? Try `/opt/mailman/mm/venv/bin/mailman info` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: invalid parameter response of the rest-api

by gioklr71＠gmail.com

Hi Mark, in the end you were right! I printed the dictionary items (email, name) and entered them via Postorius and found a wrong address. After correcting the address the APIs worked. Let's say that the reporting of the wrong email format in the code is not very clear .... In any case, problem solved. Thank you very much for your time! Gianni

2 years, 10 months

Sanity check of upgrade procedure

by David Newman

The other day Abhilash posted here that updated releases are available. I rarely upgrade my Mailman3 server running in a venv on Debian 11. But when I have there was previously an issue with mistune, requiring commands like this (run as mailman in a venv): pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi pip install wheel mailman pymysql mysqlclient pip install mistune==2.0.0rc1 mailman-web migrate mailman-web compress mailman-web collectstatic mailman-web compilemessages For these new releases, is that mistune step still needed? Thanks! dn

2 years, 9 months

Re: Weird startup problem after upgrade

by Mark Sapiro

On 12/2/22 08:21, Odhiambo Washington wrote: > > Secondly, it appears that the upgrade did NOT change the versions for the > upgraded components - postorius=1.3.6, hyperkitty=1.3.5, > Mailman Core Version=3.3.5. I was expecting the version to all bump up to > the latest. Your `pip freeze` at https://pastebin.ubuntu.com/p/tMGDxjKwJ8/ shows django-mailman3==1.3.8 HyperKitty==1.3.6 mailman==3.3.7 mailman-hyperkitty==1.2.0 mailmanclient==3.3.4 postorius==1.3.7 which are the latest. Perhaps you have older versions installed outside the venv and perhaps this confusion is the cause of your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

Mailman-users search results for query "Postorius"