Mailscanner 4.50.12-2 upgrade stops working

[Craig White]

On Sun, 2006-01-29 at 00:00 +0100, Patrick de Brabander wrote:
> I´ve installed the new beta 4.50.12-2 over my working MailScanner-4.50.10-1.
> New mail in arriving in the mail box and in my log file is see the following
>  
> Jan 28 22:57:51 server MailScanner: MailScanner -15 succeeded
> Jan 28 22:57:51 server MailScanner: succeeded
> Jan 28 22:57:52 server MailScanner: succeeded
> Jan 28 22:58:00 server postfix: succeeded
> Jan 28 23:14:06 server postfix: succeeded
> Jan 28 23:14:14 server last message repeated 2 times
> Jan 28 23:14:23 server MailScanner: MailScanner -15 succeeded
> Jan 28 23:14:23 server MailScanner: succeeded
> Jan 28 23:14:34 server last message repeated 3 times
> Jan 28 23:14:39 server root: MailScanner setting GID to postfix (89) 
> Jan 28 23:14:39 server root: MailScanner setting UID to postfix (89) 
> Jan 28 23:14:40 server MailScanner: succeeded
> Jan 28 23:15:35 server postfix: Process did not exit cleanly, returned 255
> with signal 0 
> Jan 28 23:16:08 server last message repeated 3 times
> Jan 28 23:17:14 server last message repeated 6 times
> Jan 28 23:18:20 server last message repeated 6 times
> Jan 28 23:19:26 server last message repeated 6 times
> Jan 28 23:20:32 server last message repeated 6 times
> Jan 28 23:21:39 server last message repeated 6 times
> Jan 28 23:22:45 server last message repeated 6 times
> Jan 28 23:23:51 server last message repeated 6 times
> Jan 28 23:24:57 server last message repeated 6 times
> Jan 28 23:26:03 server last message repeated 6 times
> Jan 28 23:27:10 server last message repeated 6 times
> Jan 28 23:27:21 server postfix: Process did not exit cleanly, returned 255
> with signal 0 
> Jan 28 23:27:22 server postfix: succeeded
> 
> 
> Can somebody help me.
> 
> Is it possible to go back to an older version. 
----
I believe that this has come up before. This isn't an issue with
versions, this is an issue with postfix being unable to find it's 'K'
scripts in SysV. If this is a redhat type system...

chkconfig --add postfix
chkconfig postfix off

should fix this.

Craig