Currently I'm using all the pythonfilters shipped with 0.6
Don't use the dialback filter. It's known to cause Python to deadlock.
Oh, bummer! :) Well, that explains why I would experience this kind odd behaviour then... Other than that, I must say that it is a _really_ efficient way to kick the spammers out
/me nods
I'd really like to figure it out, but it's tough. gdb won't attach to the python process when it's deadlocked, and I'm not really sure I understand using gdb in a multithreaded process well enough. Anyone know if/how you can attach to the first thread and get a backtrace on other threads?
I'm no Python programmer, but I would suspect that this is some Python internal deadlock?
Seems that way to me.
For the record this is Python 2.2.1 on a RedHat 8.0 box (latest updates available), but would Python 2.3.x help in any way?
Haven't tested on 2.3.
Any ideas why this deadlock is happening, is it thread related, or something completely different?
It's almost certainly thread related.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
