I'm trying to configure a Mailman 2.1.6 installation to have an
open-posting list. That is, mail from nonmembers should be immediately
accepted and forwarded to the list.
In Privacy Options -> Sender Filters, I have generic_nonmember_action set
to Accept. I also have accept_these_nonmembers s
I'm running about 20-30 lists on Mailman 2.0.13. There's one particular
list that's having problems with both lockfiles showing up in
$MAILMAN_HOME/locks/ and config.db.tmp.* files showing up in
$MAILMAN_HOME/lists/listname/
The PID referenced in the config.db.tmp file shows up as being:
[minter
Is there an easy way to unsubscribe people from a list who've been
bouncing and are thus set to "nomail"?
--Wade
--
If you have a VCR or MP3 player, you need to read these links:
http://www.digitalconsumer.org/
http://digitalspeech.org/
http://www.libertyboard.org/
--
This weekend, my error logs started filling up with this error:
Jul 20 16:12:01 2002 (80580) Delivery exception: EOF read where object
expected
Jul 20 16:12:01 2002 (80580) Traceback (most recent call last):
File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in
do_pipeline
func(m
On Tue, 16 Jul 2002, H. Wade Minter wrote:
> All other lists on this server work fine - you can get in with no
> problems. There is nothing showing up in the mailman logs or httpd logs.
> The only clue I have is a process that shows up in the ps list:
>
> nobody 83092 0.0
I downgraded from 2.0.12 to 2.0.11 due to the issues I reported to the
list yesterday.
Today, a list client contacted me that they couldn't log into their
/admin/listname/ interface. I tried it out, and sure enough, you press
"Let me in..." and the web browser just hangs while sending the reques
I upgraded over the weekend to Mailman 2.0.12, and got up this morning
to find hundreds of entries in my qfiles/ directory.
I'm running into the same problem reported by Armour Van Horn on
Saturday, namely an errors logfile full of:
###
Jul 12 23:41:21 2002 qrunner(1355): Traceback (innermost
