Peter Radcliffe wrote: > >Makes me really puzzled.
Me too. >My best guess is I changed the mm_cfg.py file >from when I had the bad entries in, post-upgrade, and afterwards only >processes not in the mailman group that couldn't write to >Mailman/mm_cfg.pyc were run until I was done testing... This wouldn't be the explaination. If the .py is newer than the .pyc, the .py should always be used whether or not the .pyc can be updated. >but my MTA is >in mailman group and runs the wrapper as mailman/malman so that >doesn't make much sense. > >Very odd. Thanks for the debugging help, though. I'm glad it is working as it should. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
