Mark Sapiro ha scritto: > Was this at the time that you restarted Mailman?
Yes, possibly it was that time... In fact so far my solution to the problem has been a cron job which sends a SIGHUP signal to outgoin runner once a day at a fixed time, just to fix the situation in case something was wrong, and sometimes in correspondece to the time of that cron job I can find a similar entry in the error log. I read in some other posts in this list that possibly a cron job like this is not a good idea since it can happens that the runner is busy when it receives the signal, but so far this is the only (partial and easy) cure I can think of... :-) Thank you, Paso ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
