On 5/16/19 10:33 AM, John Griessen wrote:
I've been reading https://wiki.list.org/DOC/Mailman%203%20installation%20experience
and see that a virtual is recommended, which is not something I have done yet, and wonder if just putting the mm3 on a different server is easier?
I am the author of that document. I started with virtualenv because my first Mailman 3 installation used the now obsolete mailman-bundler and it installed things in virtualenvs.
It is not at all necessary to use virtualenv. Note that the first paragraph of the "Installation" section in that document says:
For these installs, I opted to install the entire Mailman suite in a virtualenv. The biggest motivation for this choice was the fact that there are already production lists on both servers and using a virtualenv allowed me to do a lot of the work in advance without interfering with the production install. Possibly influenced by these experiences, I am now using virtualenv for all installs.
There are pros and cons to using a virtualenv. The big plus is it isolates your installation and avoids conflicts due to the installed software requiring versions of dependencies that are different from those that might be installed and required system wide. It also avoids the need to install as root although things like web server and MTA configuration still require root. The downside is a potentially larger footprint in the file system.
I have a server, mail1.cibolo.us that has postfix, postgresql, dovecot, mm2, nsd on it. Another server has just web pages and nsd doing backup DNS for mail1.cibolo.us DNS server. I could do a straight debian install of mailman3-full on the 2nd server and keep it simple, let debian setup a blank database installation, right? Has anyone seen a good write up on how to do that on a debian server step by step?
I can't speak to the installation of the Debian package. It should be straightforward, but I don't really know. The one potential glitch is if you don't have an MTA on the Mailman server. This is doable. Mailman has it's own LMTP server to receive mail and can be configured to use a remote MTA to deliver mail. Mailman also generates transport mappings to control delivery of mail to Mailman and these get updated when lists are added or deleted. There is a configurable postmap_command which is invoked when the maps are updated to update the .db files. That can point to a shell script to rsync the files to the other server if needed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan