[Mailman-Users] Installing Mailman on OS X El Capitan--can’t find source of erroneous call of binary at /usr/share/mailman/mail/mailman

Dominik Hoffmann dhoffmann at uwalumni.com
Tue Oct 11 16:46:22 EDT 2016


I have followed Allan Herman's March 29, 2013, instructions for installing Mailman on OS X Mountain Lion. The difference is that my system is OS X El Capitan running Server 5.2. Nonetheless, I have not run into any contradictions. It appears that the choices for the locations of the various configuration files made when transitioning from Mac OS X Snow Leopard to Mac OS X Lion to OS X Mountain Lion have remained stable.

However, I am now banging my head against the wall, because my server's SMTP logs contain these lines:

Oct 11 16:04:04 i----on local[56963]: fatal: execvp /usr/share/mailman/mail/mailman: No such file or directory

Allan installs his Mailman deployment in /usr/local/, and I have learned that in one of the more recent iterations of OS X, Apple chose to lock down /usr/share/, so that even the sudo command does not make modifications possible, which I learned, when I tried to create a simlink there. I kept getting the "Operation not permitted." error. I learned that this is due to System Integrity Protection (SIP), introduced in OS X El Capitan.

I am now on a quest to locate from where the call to mailman originates, so that I can edit the corresponding configuration file, replacing "/usr/share/" with "/usr/local/".

Any pointers would be much appreciated.

Dominik Hoffmann

More information about the Mailman-Users mailing list