After installing Mailman I receive the following message, one per minute.
Traceback (most recent call last):
File "/home/mailman/cron/qrunner", line 275, in ?
lock.lock(timeout=0.5)
File "/home/mailman/Mailman/LockFile.py", line 219, in lock
self.__write()
File "/home/mailman/Mailma
Interesting, I just saw this exact question answered a few days ago, and
that answer was to upgrade to Mailman 2.07
There is a bug in 2.06 that allows certain bounces formated just wrong, to
muck-up mailman and cause it to freeze. If you find the offending mail in
your queue (and remove it),
Has anyone else noticed that these documents are not accessable?
www.aurora.edu seems to be dead.
--a
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Hi, gang,
I have searched the archives, and have seen many questions similar to
mine, but no answers. I'm sorry that I'm asking the same question, but
I'm stumped.
I have a list run by Mailman 2.0.6 that has, all of a sudden, decided
that it will not distribute messages. It was working fine la
I thought I had this one taken care of, but no go this morning on the
big switch-over...
I have a machine with ~650 lists. Somehow, they refuse to let
individual users subscribe themselves to lists through the web or an
email, yet an admin can still add them through the web or from the
comma
