Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-04 Thread Steve Matzura
On Sat, 04 Jul 2015 08:54:44 -0700, Mark Sapiro wrote: >The RedHat/Centos package is even more complex. See the FAQ at >. Thanks. Noted and saved for future reference. -- Mailman-Users mailing list Mailman-Users@

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-04 Thread Mark Sapiro
On 07/04/2015 08:23 AM, Steve Matzura wrote: > > Because that's the only one I knew of. Blame Red Hat for this one. :-) The RedHat/Centos package is even more complex. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, C

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-04 Thread Steve Matzura
On Sat, 04 Jul 2015 07:22:43 -0700, Mark wrote: >Mailman has two main configuration paths, $prefix for immutable code, >etc. and $var_prefix for mutable data. By default, $var_prefix = >$prefix, but in your case, you or the packager whose package you >installed configured mailman with $prefix=/usr

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-04 Thread Mark Sapiro
On 07/03/2015 03:59 PM, Steve Matzura wrote: > > Interesting: My $prefix is /usr/lib/mailman. However, there is a > /var/lib/mailman as that's where archives is. It's owned and grouped > properly, and it does have the 1-bit set in the 'other' portion of its > permissions mask. I can definitely fix

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-04 Thread Steve Matzura
On Fri, 03 Jul 2015 06:50:58 -0700, you wrote: >$prefix/archives and the private/ and public/ sub-directories thereof >are created on installation, and if Mailman is running there must be a >'mailman' site list and thus $prefix/archives/private/mailman/ and >$prefix/archives/private/mailman.mbox/

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-03 Thread Mark Sapiro
On 07/03/2015 03:24 AM, Steve Matzura wrote: > > Understood. Since this is really a new installation (I didn't copy > archives from the old system because they're not really of any use), > $prefix/archives doesn't exist yet. I'll keep the above in mind and > implement it when list traffic commence

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-03 Thread Steve Matzura
On Thu, 02 Jul 2015 16:39:36 -0700, you wrote: >> After check_perms fixed all problems, I re-ran it and got this: >> >> Warning: Private archive directory is other-executable (o+x). >> This could allow other users on your system to read private >> archives. >> If you're on a sha

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-02 Thread Mark Sapiro
On 07/02/2015 09:01 AM, Steve Matzura wrote: > On Thu, 02 Jul 2015 08:24:12 -0700, you wrote: > >> Run check_perms. > > Did that. 898 problems found! I hope I didn't break Postfix. Luckily I > logged before and after in case I have to revert. Check_perms only affects files and directories in Ma

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-02 Thread Steve Matzura
On Thu, 02 Jul 2015 08:24:12 -0700, you wrote: >On 07/02/2015 07:56 AM, Steve Matzura wrote: >> If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the >> following: >> >> Bug in Mailman version 2.1.18-1 >> >> Bug in Mailman version 2.1.18-1 >> We're sorry, we hit a bug! >> >> Pl

Re: [Mailman-Users] Unable to access Mailman Web interface

2015-07-02 Thread Mark Sapiro
On 07/02/2015 07:56 AM, Steve Matzura wrote: > If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the > following: > > Bug in Mailman version 2.1.18-1 > > Bug in Mailman version 2.1.18-1 > We're sorry, we hit a bug! > > Please inform the webmaster for this site of this problem. P

[Mailman-Users] Unable to access Mailman Web interface

2015-07-02 Thread Steve Matzura
If I browse to http://{my-node.my-domain.com}/mailman/admin, I get the following: Bug in Mailman version 2.1.18-1 Bug in Mailman version 2.1.18-1 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been expl