On Fri, Apr 7, 2023 at 12:29 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
On Fri, Apr 7, 2023 at 7:14 PM Dave Hall via Mailman-users < mailman-users@mailman3.org> wrote:
Hello,
I know that installing from Debian packages is not the preferred method - unfortunately that's what I'm stuck with at the moment. I have an installation that is sort of working, but there seems to be a lot of issues relating to ownership and permissions that I'll have to manage by hand, so I am asking for some guidance.
It's actually not that difficult to migrate from the Debian packages to the virtualenv setup.
It's not an option for me today. Migration might be easy, but it's a different path for bringing code onto my servers - auditing and security. Someday soon I'd like to move this to Kubernetes or something, but not today. Today I need to move servers from Debian 10 to Debian 11, and Mailman 2.1 is disappearing so I need to migrate native Debian Mailman 2 to native Debian Mailman 3 as quickly as possible.
I'm seeing an interplay between 'list' (the existing Mailman2 user), www-data (the Apache user) and root. Given that it seems like almost everything that's part of mailman3-web/django/hyperkitty is running in uwsgi, should I maybe change /etc/mailman3/uwsgi.ini to use 'list' as the uid/gid rather than www-data and then also change any user/group permission to 'list' as well?
Mailman3 components (Core, Django) only needs read permissions to /etc/mailman3/*, nothing more. Web-wise, MM2 and MM3 can even co-exist on the same server. Only the core will have issues should you share the listnames.
In addition to /etc/mailman3/*, there's also /var/lib/mailman3 and
/var/log/mailman3. I'm seeing this mixture of owner/group as well in these folders and their subfolders.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
-- Dave Hall Binghamton University