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

2016-10-13 Thread 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

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

2016-10-12 Thread 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: > >

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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

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

2016-10-12 Thread 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