Dear all I used the following when setting up Mailman 2.14: ./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=www --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python To upgrade PHP from 5.2 to 5.3 the website hosts have to enable suexec (I don't quite understand this but bear with me!) which breaks Mailman, I think because it runs as a different user to before. Can I reconfigure Mailman using this? ./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=users --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python This is the with-cgi-gid setting that the hosting people suggest, but I would be grateful for confirmation from someone on this expert list. What else would I need to do? Thanks very much in anticipation. Jon
On 12/16/2013 02:42 PM, Jon 1234 wrote:
Can I reconfigure Mailman using this? ./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=users --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python This is the with-cgi-gid setting that the hosting people suggest, but I would be grateful for confirmation from someone on this expert list. What else would I need to do?
You probably need --with-cgi-gid=mailman, not --with-cgi-gid=users
See the FAQ at http://wiki.list.org/x/toA9.
You probably need --with-cgi-gid=mailman, not --with-cgi-gid=users
See the FAQ at http://wiki.list.org/x/toA9.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks. I'll try that.
Just to check, is this the correct process? mailmanctl stop -- configure (with options as in previous emails) -- make install -- mailmanctl start. I'm note sure whether it's necessary to 'make install' again.
I will make backups first, but if it all goes wrong, could I just reconfigure Mailman back to the original way and ask for suexec to be disabled again?
Thanks again
Jon
On 12/17/2013 06:36 AM, Jon 1234 wrote:
Just to check, is this the correct process? mailmanctl stop -- configure (with options as in previous emails) -- make install -- mailmanctl start. I'm note sure whether it's necessary to 'make install' again.
Yes it is necessary to make install as this is what updates the mailman/cgi-bin/* wrappers which is what needs to be done.
I will make backups first, but if it all goes wrong, could I just reconfigure Mailman back to the original way and ask for suexec to be disabled again?
I don't see why not.
Date: Tue, 17 Dec 2013 10:04:01 -0800 From: mark@msapiro.net To: mailman-users@python.org Subject: Re: [Mailman-Users] Reconfiguring Mailman with different with-cgi-gid
On 12/17/2013 06:36 AM, Jon 1234 wrote:
Just to check, is this the correct process? mailmanctl stop -- configure (with options as in previous emails) -- make install -- mailmanctl start. I'm note sure whether it's necessary to 'make install' again.
Yes it is necessary to make install as this is what updates the mailman/cgi-bin/* wrappers which is what needs to be done.
Sorry to resurrect this.
- When I tried to run configure, I realised the configure file wasn't there. I downloaded the same version - 2.1.15 - and used the file from there. Was this the right place to get the configure file?
- It looked like the new configure options would have worked. Does that look right?checking for --with-username... [my username]checking for user name "[my username]"... okaychecking for --with-groupname... userschecking for group name "users"... okaychecking permissions on /[my path]/mailman... okay
- Configuration stopped because a file was missing. Each time I uploaded the missing file from the recent download, the next attempt stopped for another file. I gave up as obviously I was barking up the wrong tree. I assume I used to have these files so what went wrong? Here they are:config.status: error: cannot find input file: misc/paths.py.inconfig.status: error: cannot find input file: Mailman/Defaults.py.inAlso.... install-sh, src/, misc/, Mailman/Defaults.py.in...
- *IF* the answer is to install from scratch then move across the archive, could or should I use the latest version 2.1.17?
Thanks in anticipation. If you require further information please let me know. Best wishes Jon
On 04/07/2014 11:18 AM, Jon 1234 wrote:
- *IF* the answer is to install from scratch then move across the archive, could or should I use the latest version 2.1.17?
Thanks in anticipation. If you require further information please let me know.
Download the 2.1.17 tarball, unpack it and run configure, make and sudo make install in the unpack directory which must not be the installation directory.
Install it over your existing installation, and everything should be fine, you shouldn't have to move anything.
From: mark@msapiro.net Download the 2.1.17 tarball, unpack it and run configure, make and sudo make install in the unpack directory which must not be the installation directory.
Install it over your existing installation, and everything should be fine, you shouldn't have to move anything.
I see mention of version 2.1.18 in the FAQ about DMARC. How long until 2.1.18 is released? (I can wait.) I really appreciate the responses, thank you.
Jon
On 04/16/2014 03:28 PM, Jon 1234 wrote:
I see mention of version 2.1.18 in the FAQ about DMARC. How long until 2.1.18 is released? (I can wait.) I really appreciate the responses, thank you.
It will be very soon. A candidate within a week or so and final maybe early May.
-
Jon 1234 -
Mark Sapiro