Re: [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]

/usr/local/mailman/bin/genaliases did do the trick. Thanks so much, Mark!

> On Oct 12, 2016, at 3:10 PM, Dominik Hoffmann  wrote:
> 
> I think, actually, that that may have done the trick. I started getting some 
> test messages I had sent to the list earlier, which must have been queued. I 
> will have to do more testing later, when I have time.
> 
>> On Oct 12, 2016, at 11:36 AM, Dominik Hoffmann  
>> wrote:
>> 
>> /usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
>> that it didn't change anything or simply did so silently?
> --
> Mailman-Users mailing list Mailman-Users@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/dhoffmann%40uwalumni.com

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [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]

I think, actually, that that may have done the trick. I started getting some 
test messages I had sent to the list earlier, which must have been queued. I 
will have to do more testing later, when I have time.

> On Oct 12, 2016, at 11:36 AM, Dominik Hoffmann  wrote:
> 
> /usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
> that it didn't change anything or simply did so silently?
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [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]

/usr/local/mailman/bin/genaliases did not produce any output. Does this mean 
that it didn't change anything or simply did so silently?

> On Oct 12, 2016, at 11:24 AM, Mark Sapiro  wrote:
> 
> On 10/12/2016 08:16 AM, Mark Sapiro wrote:
>> 
>> I don't know how these aliases are generated in your setup, but assuming
>> you have Mailman's Postfix integration, that path comes from the
>> WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
>> EXEC_PREFIX which is often the same as PREFIX. These things are set from
>> options to configure when Mailman is configured.
>> 
>> Did you start your installation by running configure? If so, what is the
>> configure command from config.log, is there a --prefix= option or a
>> --exec-prefix= option - the defaults for these are
>> --prefix=/usr/local/mailman and --exec-prefix=(the prefix value).
>> 
> 
> 
> Or perhaps everything is configured correctly but your Postfix aliases
> are just left from a prior install and all you need do is run Mailman's
> bin/genaliases.
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@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/dhoffmann%40uwalumni.com

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [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]

Thanks for the offer! I don't think, I want to go the MacPorts route at this 
point. I am thinking about it, though!

> On Oct 12, 2016, at 11:16 AM, Timothy Jasionowski  
> wrote:
> 
> I’m one of the few people who has blazed this trail on the newer versions of 
> OS X Server, mainly using the macports installation method with a few 
> modifications.  If you want to email me off the list, I can share my 
> insights.  Alternately, search the archives for my previous posts/fixes for 
> this, as I’ve tried to document my challenges.
> 
> Timothy
> 
>> On Oct 11, 2016 (Wk 42), at 4:46 PM, Dominik Hoffmann 
>>  wrote:
>> 
>> Hi:
>> 
>> 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 ion 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
>> 
>> 
>> --
>> Mailman-Users mailing list Mailman-Users@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
> 

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

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

[Mark Sapiro]

On 10/12/16 8:34 AM, Dominik Hoffmann wrote:
> Thanks very much!
> 
> I looked through Defaults.py and found
> 
> PYTHON  = '/usr/bin/python'
> PREFIX  = '/usr/local/mailman'
> EXEC_PREFIX = '${prefix}'
> VAR_PREFIX  = '/usr/local/mailman'


See my follow-up at
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

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

[Timothy Jasionowski]

I’m one of the few people who has blazed this trail on the newer versions of OS 
X Server, mainly using the macports installation method with a few 
modifications.  If you want to email me off the list, I can share my insights.  
Alternately, search the archives for my previous posts/fixes for this, as I’ve 
tried to document my challenges.

Timothy

> On Oct 11, 2016 (Wk 42), at 4:46 PM, Dominik Hoffmann 
>  wrote:
> 
> Hi:
> 
> 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 ion 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
> 
> 
> --
> Mailman-Users mailing list Mailman-Users@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

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [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]

Thanks very much!

I looked through Defaults.py and found

PYTHON  = '/usr/bin/python'
PREFIX  = '/usr/local/mailman'
EXEC_PREFIX = '${prefix}'
VAR_PREFIX  = '/usr/local/mailman'

This looks normal to me and is verbatim from Allan Herman's instructions, which 
get their configure call from Larry Stone's May 1, 2010, instructions (also on 
this mailing list):

./configure --prefix=/usr/local/mailman --with-cgi-gid=_www 
--with-mail-gid=_mailman

I can't find any reference to "--exec-prefix=" in config.log.

Dominik

> On Oct 12, 2016, at 11:16 AM, Mark Sapiro  wrote:
> 
> On 10/11/2016 01:46 PM, Dominik Hoffmann wrote:
>> 
>> 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 ion 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/".
> 
> 
> It comes from PID 56963 which looks like a Postfix 'local' delivery
> agent instance. I.e., it's in your Postfix aliases.
> 
> I don't know how these aliases are generated in your setup, but assuming
> you have Mailman's Postfix integration, that path comes from the
> WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
> EXEC_PREFIX which is often the same as PREFIX. These things are set from
> options to configure when Mailman is configured.
> 
> Did you start your installation by running configure? If so, what is the
> configure command from config.log, is there a --prefix= option or a
> --exec-prefix= option - the defaults for these are
> --prefix=/usr/local/mailman and --exec-prefix=(the prefix value).
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@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/dhoffmann%40uwalumni.com

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

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

[Mark Sapiro]

On 10/12/2016 08:16 AM, Mark Sapiro wrote:
> 
> I don't know how these aliases are generated in your setup, but assuming
> you have Mailman's Postfix integration, that path comes from the
> WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
> EXEC_PREFIX which is often the same as PREFIX. These things are set from
> options to configure when Mailman is configured.
> 
> Did you start your installation by running configure? If so, what is the
> configure command from config.log, is there a --prefix= option or a
> --exec-prefix= option - the defaults for these are
> --prefix=/usr/local/mailman and --exec-prefix=(the prefix value).
> 


Or perhaps everything is configured correctly but your Postfix aliases
are just left from a prior install and all you need do is run Mailman's
bin/genaliases.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

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

[Mark Sapiro]

On 10/11/2016 01:46 PM, Dominik Hoffmann wrote:
> 
> 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 ion 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/".


It comes from PID 56963 which looks like a Postfix 'local' delivery
agent instance. I.e., it's in your Postfix aliases.

I don't know how these aliases are generated in your setup, but assuming
you have Mailman's Postfix integration, that path comes from the
WRAPPER_DIR setting in Mailman/Defaults.py. That in turn is based on
EXEC_PREFIX which is often the same as PREFIX. These things are set from
options to configure when Mailman is configured.

Did you start your installation by running configure? If so, what is the
configure command from config.log, is there a --prefix= option or a
--exec-prefix= option - the defaults for these are
--prefix=/usr/local/mailman and --exec-prefix=(the prefix value).

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[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]

Hi:

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 ion 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


--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org