version 1.1.32 of the DCC

Rose, Bobby
Wed Mar 12 15:12:00 UTC 2003

Hmm it seems that it only does it the first minute or two after
starting.  I checked my log folder and there were only 5 tmp files.
Now it's just back to the regular intermittent timeouts.

-----Original Message-----
From: Vernon Schryver [] 
Sent: Tuesday, March 11, 2003 7:36 PM
Subject: RE: version 1.1.32 of the DCC

> From: "Rose, Bobby" <>

> I just updated to 1.1.32 from 1.1.27 and I'm seeing some new errors in

> the mail log.
> Mar 11 17:04:45 eeyore dccm[23251]: [ID 942336 mail.notice] 1.1.32 
> listening to /var/run/dcc/dccm with /var/dcc Mar 11 17:05:55 eeyore 
> sendmail[22535]: [ID 801593 mail.error]
> h2BM2pXb022535: Milter (dcc): write(Q) returned -1, expected 5: Broken

> pipe Mar 11 17:05:55 eeyore sendmail[22535]: [ID 801593]
> h2BM2pXb022535: Milter (dcc): to error state
> Now it's not happening everytime but is frequent enough to stand out 
> as something being wrong.

That could be bad, because it suggests the dccm thread closed its end of
the pipe.  
Is the size of the dccm process growing?  Are tmp.* files accumulating
in the log directory?

On the other hand, I've seen the sendmail milter library time out while
waiting for sendmail to get all of a message from the distant SMTP
client, and cause that sort of complaint.

Someone else sent me several hundred tmp.* files that seem related to a
bloating dccm process.  I've feed most of them through sendmail+dccm
without seeing anything odd on FreeBSD or BSD/OS with sendmail 8.12.8.

Vernon Schryver
DCC mailing list

More information about the DCC mailing list

Contact by mail or use the form.