[Mimedefang] Slave in killed status after SA 3.1

[Marc Harding]

David, I am on the digest version and have not yet received your reply,
however I did see it on the list web page.

Anyways, when I do the mimedefang.pl -features, it does say that that I am
2.53.  Here is the rest of the perl information in case that may help:


MIMEDefang version 2.53

...

Anomy::HTMLCleaner            : Version 1.24
Archive::Zip                  : Version 1.14
Digest::SHA1                  : Version 2.10
File::Scan                    : Version 1.43
HTML::Parser                  : Version 3.36
HTML::TokeParser              : Version 2.28
IO::Socket                    : Version 1.27
IO::Stringy                   : Version 2.109
MIME::Base64                  : Version 3.05
MIME::Tools                   : Version 5.417
MIME::Words                   : Version 5.417
Mail::Mailer                  : Version 1.64
Mail::SpamAssassin            : Version 3.000004
Net::DNS                      : Version 0.48
Unix::Syslog                  : Version 0.100

I reverted back to SA 3.0.4 to lower my stress level.

Regards,

Marc



Hi,
 
I installed Spamassassin 3.1 this morning and since I have been having some
slave problems not closing properly, no problems before this change.  It
seems the only way I can fix MIMEDefang is be restarting the service.  This
is an older server (RedHat 9) but I am using 2.53.  Here is the last
relevant message from the server:
 
Sep 22 11:42:43 mail mimedefang-multiplexor[1467]: Slave 0 (pid 1492) taking
too long to exit; sending SIGTERM
Sep 22 11:42:53 mail mimedefang-multiplexor[1467]: Slave 0 (pid 1492) taking
way too long to exit; sending SIGKILL
 
I am not sure what other information you require.  Please let me know if you
have any ideas.
 
Regards,
 
Marc Harding.