On Fri, 2004-07-09 at 15:22 +0300, Matti Aarnio wrote: > > 3. It seems that socket interface to the contentfilter got broken? I'd > > prefer to use it with my zmscanner (forking "zmscanner -i 0" does not > > seem to work right now). > > It should work just like before. The relevant code was moved from > contentpolicy.c to subdaemon-ctf.c and has new function names, > but otherwise it is unchanged. > Of course I have only tested the "fork and run" variant myself, not > named socket one. What is fdpass_sendfd? when socket interface to contentfilter is used, on the first try I get this: INapCMf0000# 000-smtpcontentfilter_init: fdpass_sendfd(8,13) rc=0, errno=Error 0 INapCMf0000# 000-smtpcontentfilter_init; 9 INapCMf0000# 000-smtpcontentfilter_init; 10 INapCMf0000# 000-smtpcontentfilter_init; 11; errno=Error 0 INapCMf0000# 000-smtpcontentfilter_init; 12 INapCMf0000# 000-fdgets()->61300 rc=-1 buf="" INapCMf0000# 000-Interactive contentfilter timed out! (no real timeout of course, it happens instantly). On subsequent submissions, the message is different: INjcCNN0001# 000-smtpcontentfilter_init: fdpass_sendfd(8,13) rc=-1, errno=Broken pipe INjcCNN0001# 000-Failed to init interactive contentfilter subsystem Eugene
This is a digitally signed message part