"bogus null SMFICTX pointer" messags from dccm

Vernon Schryver wrote:
> Are the "bogus null SMFICTX pointer" error messages from dccm being
> seen at more than the one site?

Last few days I will occassionally see messages like this:

Feb 10 21:36:40 inbound0 sendmail[54746]: h1B5aev7054746: 
milter_read(dcc): cmd read returned 0, expecting 5
Feb 10 21:36:40 inbound0 sendmail[54746]: h1B5aev7054746: Milter (dcc): 
to error state
Feb 10 21:36:40 inbound0 sendmail[54746]: h1B5aev7054746: Milter (dcc): 
init failed to open
Feb 10 21:36:40 inbound0 sendmail[54746]: h1B5aev7054746: Milter (dcc): 
to error state
Feb 10 21:38:17 inbound0 sendmail[54287]: h1B5T9v7054287: Milter (dcc): 
write(Q) returned -1, expected 5: Broken pipe
Feb 10 21:38:17 inbound0 sendmail[54287]: h1B5T9v7054287: Milter (dcc): 
to error state

These go away when I perform a 'libexec/rcDCC restart'.

Last time it happened we were under a large flood of spam, so I did not 
poke around other than netstat -m, which was fine.

tim