thanks...
Mark Sapiro wrote:
kalin m wrote:
hi there... wondering if fake email addresses in a mailman list can get
cleaned up with the bounces options. just testing with one and the mail
log says (correctly) it could not resolve the host. is this considered a
hard bounce by mailman?!
hi there... wondering if fake email addresses in a mailman list can get
cleaned up with the bounces options. just testing with one and the mail
log says (correctly) it could not resolve the host. is this considered a
hard bounce by mailman?! i have enabled the bounce processing, the
maximum
ON:
File "/var/mailman/Mailman/MailList.py", line 144, in __getattr__
raise AttributeError, name
AttributeError: data_version
kalin m wrote:
Mark Sapiro wrote:
kalin m wrote:
i did delete the locks when the problem begun. but that apparently
didn;t do much.. now here is what i get:
Mark Sapiro wrote:
kalin m wrote:
i did delete the locks when the problem begun. but that apparently
didn;t do much.. now here is what i get:
Do you still have lock issues? Perhaps you deleted some active lock
requests along with the stale lock and allowed a concurrent update
b.
a grep on both files for data_version is not returning anything
Mark Sapiro wrote:
kalin m wrote:
now for the same list i get:
Traceback (most recent call last):
File "/var/mailman/scripts/driver", line 87, in run_main
main()
File "/var/mailman/Mailman/Cgi/admin.p
var/mailman/Mailman/MailList.py", line 144, in __getattr__
raise AttributeError, name
AttributeError: data_version
kalin m wrote:
hi all...
mailman has been locking one list out.
the web interface just hangs and it generates a bunch of locks. it
seems that it can not write to a log
hi all...
mailman has been locking one list out.
the web interface just hangs and it generates a bunch of locks. it seems
that it can not write to a log but not sure which one. errors are like:
ep 17 05:09:12 2008 (18481) musiclist.lock lifetime has expired, breaking
Sep 17 05:09:12 2008 (1848
