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

[Mailman-Users] Cron has issues with gate_news

2016-10-13 Thread Dominik Hoffmann
There are still a few of things to mop up, after an otherwise successful installation of Mailman on OS X El Capitan with Server 5.2. Every 5 min my admin user account on the server gets an email from the Cron Daemon that has this line: IOError: [Errno 13] Permission denied:

Re: [Mailman-Users] Cron has issues with gate_news

2016-10-13 Thread Dominik Hoffmann
Another observation: 4. Moving the Crontab from root to _mailman had no effect. > On Oct 13, 2016, at 11:43 AM, Dominik Hoffmann wrote: > > There are still a few of things to mop up, after an otherwise successful > installation of Mailman on OS X El Capitan with Server

Re: [Mailman-Users] one mailing list shunting messages

2016-10-13 Thread Mark Sapiro
On 10/13/2016 09:51 AM, Knight, Eric wrote: > I am not sure what to do about this message in error log, any help > appreciated. > > > Oct 13 11:47:30 2016 (12368) SHUNTING: > 1476372076.1651051+54a50f9eb22730094aba33728b8cee7136dad7e2 > Oct 13 11:47:30 2016 (12368) Uncaught runner exception:

Re: [Mailman-Users] Cron has issues with gate_news

2016-10-13 Thread Mark Sapiro
On 10/13/2016 08:56 AM, Dominik Hoffmann wrote: > Another observation: > > 4. Moving the Crontab from root to _mailman had no effect. Good you moved it, but see below. >> On Oct 13, 2016, at 11:43 AM, Dominik Hoffmann >> wrote: >> >> There are still a few of things

[Mailman-Users] one mailing list shunting messages

2016-10-13 Thread Knight, Eric
I am not sure what to do about this message in error log, any help appreciated. Oct 13 11:47:30 2016 (12368) SHUNTING: 1476372076.1651051+54a50f9eb22730094aba33728b8cee7136dad7e2 Oct 13 11:47:30 2016 (12368) Uncaught runner exception: local variable 'bodylen' referenced before assignment Oct

[Mailman-Users] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

2016-10-13 Thread Dominik Hoffmann
My mailing lists were migrated from a machine running Mac OS X Server 10.6 (Snow Leopard) [let's refer to it by the fdqn old-server.domain.com], where mailman was supplied and supported out of the box. The destination was an OS X Server 10.11 (El Capitan) system running Server 5.2 [let's refer

Re: [Mailman-Users] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

2016-10-13 Thread Dominik Hoffmann
Great! Thanks, Mark! I ran /usr/local/mailman/bin/withlist -l -a -r fix_url and now all my lists actually show up on the "Overview of all new-server.domain.com mailing lists" page. One thing that still doesn't work is submission of the pending moderator requests. When I hit Submit

Re: [Mailman-Users] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

2016-10-13 Thread Mark Sapiro
On 10/13/2016 01:51 PM, Dominik Hoffmann wrote: > > One thing that still doesn't work is submission of the pending moderator > requests. When I hit Submit All Data, the page simply reloads without any of > the moderation directives having been taken into account. See

Re: [Mailman-Users] Administrative requests page for migrated lists uses wrong old server fqdn for data submission

2016-10-13 Thread Mark Sapiro
On 10/13/2016 12:19 PM, Dominik Hoffmann wrote: > > When editing the list settings, there were references to > "old-server.domain.com" in the host_name field on the General Options page, > and I changed that to "new-server.domain.com". > > What do I need to fix, in order for the button