Martin Blapp wrote:

> Yes, this version fixes the Problem definitly. Thanks !

Excellent news!

If this version fixes it, then there's a bug in SpamAssassin 3.1RC1
that I don't have time to track down.  It seems that somehow, when the
use Mail::SpamAssassin; code is executed, or when the
Mail::SpamAssassin->new() function is called, the SIGCHLD handler is
reset and not set back.  Looking at the code, I can't see how it can
happen, but obviously, it is happening.

Regards,

David.
_______________________________________________
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list
[email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Reply via email to