On 2016-07-13 14:53, Barry Warsaw wrote:
On Jul 13, 2016, at 10:30 AM, Jean-Luc Wasmer wrote:
Is there a way to change where mailman looks for files? I've run into many issues with the default config:
mailman is specifically calling Python 3.4, ignoring the fact that I have Python 3.5
How did you install Mailman? If it was into a virtualenv, then it will use the Python in your venv's bin directory, so if you first created it with Python 3.4, that's what you'll get.
I followed the instructions on: https://gitlab.com/mailman/mailman-bundler/ I didn't have Python 3.4 installed at all... had to install it to complete Mailman's installation.
- shell scripts expect bash to be at /bin/bash (mine is at
- /usr/local/bin/bash)
Which shell scripts? Mailman itself doesn't ship any shell scripts, so again, I'm guessing you're talking about the ones in your vent?
I'm referring to: ./bin/mailman-post-update ./bin/mailman-web-django-admin createsuperuser
- mailman expects postmap to be at /usr/sbin/postmap (mine is at
- /usr/local/sbin/postmap)
That one's easy. If you run `mailman conf | grep '\[mta\]' you will see a setting for the [mta]configuration variable, e.g.
[mta] configuration: python:mailman.config.postfix
The
python:says that the lookup scheme is via Python import path, where themailman.configpart says that it's in the mailman.config package, and thepostfixpart says that the configuration file is postfix.cfg inside that path.If you look in postfix.cfg, you'll see a
postmap_commandsetting, and this is what points to /usr/sbin/postmap by default. Change that to point to /usr/local/sbin/postmap and restart Mailman.
Thanks Barry!
Cheers, Jean-Luc