On 10/15/20 2:07 AM, Onyeibo Oku wrote:
In the meantime, I moved to option #3 (recommended for production). I hit a grey area when setting up the virtual environment. At https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-insta..., I see:
$ cd /opt/mailman $ python3 -m venv venv
The documentation imply that a 'user' creates the virtual environment but is not explicit about that 'user'.
The user can be any user you want. I use mailman on my production
installations and mark on my development installation.
The key is that user should be set as owner of /opt/mailman and then creating the venv and subsequent steps are all done as that user.
(1) Is it better to have a dedicated user (say 'mailman') then use that while following the docs? I see a lot of docs referring to a 'mailman' user. Installing mailman3 from distribution repository introduced a 'mailman' user to my box (with special UID). There has to be reasons for that.
Yes, a dedicated Mailman user is best.
(2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?)
No. setup should proceed as the Mailman user.
(3) How about using an already existing local user? What are the implications?
That's OK, but there are potential security implications due to the fact that the Mailman processes running as that user have access to all that user's non-mailman stuff.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan