[Mailman-Users] nightly_gzip sends message to mailman, gets stuck

[Kai Schaetzl]

I created new lists by copying existing directories and made the necessary 
changes with withlist etc., but these lists didn't have their archive 
directories yet. nightly_gzip barked about that (bogus archive directory 
for mailing list ...) and then sent this message to the mailman mailing 
list. There it gets stuck, as it seems because root isn't a member of the 
list. Is this expected behavior or should I change something so it gets 
distributed to the list? And if I do so what will happen? The list doesn't 
have any members.

    Liste:   Mailman at hostname
    Von:     root at hostname
    Betreff: Cron <mailman at n7> /usr/bin/python -S 
/usr/local/mailman/cron/nightly_gzip


Kai

-- 

Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org