[Mailman-Users] Update mailman MacServer5

[Timothy Jasionowski]

I think I may have sent this directly, but...

Mattias,

I had good luck installing mailman on El Capitan/Server 5 using MacPorts, as it manages all the dependencies and integrates all the chron jobs and startup stuff, but due to some legacy issues with the MacPorts configuration file, the build appends the .cgi prefix in the URI construction. It, otherwise, works fine. It avoided a lot of the issues you had in configuring it and, more importantly, maintaining it. 

If you want to get rid of the extension, download macports, refresh the build index, then edit the macports mailman build file, replacing:

configure.args      --with-cgi-ext=.cgi \
                 --with-cgi-gid=${cgigroup} \

with

configure.args      --with-cgi-gid=${cgigroup} \

Thanks again to Marius Schamschula for that tip, as it drove me crazy. 

Timothy

Sent from my iPhone

> On Sep 4, 2016, at 11:53, Mark Sapiro <mark at msapiro.net> wrote:
> 
>> On 09/04/2016 01:56 AM, Matthias Schmidt via Mailman-Users wrote:
>> sorry for being such a pain today _/\_
>> 
>> now the webinterface is not coming up.
>> It looks like the cgi is not executed instead a 404 error is generated
>> 
>> my mailman.conf for apache looks like that (it’s basically the same as on 10.6, I just changed the path):
>> 
>> ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"
> 
> 
> This is OK, but ...
> 
> 
>> Alias /pipermail/ "/var/mailman/archives/public/"
>> <Directory "/var/mailman/archives/public/">
>>    Options FollowSymLinks MultiViews Indexes
>>    AllowOverride None
>>    Order allow,deny
>>    Allow from all
>> </Directory>
>> 
>> it is included with http.conf
>> 
>> for the site I have a redirect:
>> RewriteCond %{HTTP_HOST}%{REQUEST_URI} ^liste\.dinj\.de.$
>> RewriteRule ^/(.*) https://%{SERVER_NAME}/mailman/listinfo/dinj  [L,R=permanent]
>> and that stuff was working on 10.6
> 
> 
> And all that does is redirect 'http(s)://liste.dinj.de/' to
> 'https://%{SERVER_NAME}/mailman/listinfo/dinj'
> 
> 
>> the logs say this:
>> [Sun Sep 04 17:41:42.375938 2016] [:debug] [pid 95364] mod_hfs_apple2.c(397): [client 127.0.0.1:59199] mod_hfs_apple: Allowing access with matching directory. filename = /WebFolder/dinj/mailman
>> [Sun Sep 04 17:41:42.375977 2016] [core:info] [pid 95364] [client 127.0.0.1:59199] AH00128: File does not exist: /WebFolder/dinj/mailman/listinfo/dinj
> 
> 
> So why is Apache looking for /WebFolder/dinj/mailman/listinfo/dinj? Is
> /WebFolder/dinj the DocumentRoot?
> 
> Does this happen with any mailman URL? If you go to
> 'https://liste.dinj.de/mailman/admin/dinj' do you get a similar 404 or
> only if you go to' https://liste.dinj.de/'.
> 
> Somehow your 'ScriptAlias /mailman/' directive is not effective. In a
> more or less normal apache configuration it is not sufficient to put
> mailman.conf in /etc/apache2/conf.d/, you must also have a symlink to it
> in /etc/apache2/conf-enabled/. I have no idea if this applies to Mac OX
> X Server, but you need to look at your Include and IncludeOptional
> directives in the main apache2.conf or whatever it's called to ensure
> that mailman.conf is directly or indirectly included.
> 
> 
>> /usr/local/mailman/cgi-bin/ has permissions set to 775
> 
> 
> It should be 2775 (drwxrwsr-w) but the important thing is the files
> therein should be 2755 (-rwxr-sr-x).
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/timothy.d%40jasionow.ski