"bogus null SMFICTX pointer" messags from dccm

Vernon Schryver vjs@calcite.rhyolite.com
Tue Feb 11 22:25:28 UTC 2003


> From: Tim Wicinski <tim@meer.net>

> ...
> 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 seem to differ from the bogus null pointer messages.  They smell
like the effects of the limits on the maximum number of threads/jobs
that dccm can tolerate not matching sendmail's limits on the maximum
number of simultaneous SMTP transactions.


Vernon Schryver    vjs@rhyolite.com



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.