On Wed, 14 Oct 2020 08:53:23 -0700 Mark Sapiro <mark@msapiro.net> wrote:
#!/bin/bash exec /opt/mailman/mm/venv/bin/mailman
-C "/opt/mailman/mm/mailman.cfg"
$@
Greetings Mark,
I gave up on setting up mailman using option #2 while following https://docs.mailman3.org/en/latest/install/install.html (there are lots of unknowns on that route. Certainly, the packagers are considering a lot of things that are not immediately apparent to users). Perhaps, we will see elaborate guides/docs soon.
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'.
OUTPUT: Error: [Errno 13] Permission denied: '/opt/mailman/venv'
This is expected. Which makes me wonder ... hmm, how did you do it?
(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.
(2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?)
(3) How about using an already existing local user? What are the implications?
Regards Onyeibo