dccd-1.1.21

Vernon Schryver vjs@calcite.rhyolite.com
Sun Jan 26 04:30:31 UTC 2003


> From: John Payne <john@sackheads.org>

> >> Jan 25 18:20:12 haybaler dccd[28544]: drop request from 207.8.219.201

> >> Interestingly, .201 is a different interface on .219 - this could be
> >> related...

> > Is there any chance that 207.8.219.201 has forgotten the right DCC
> > client-ID for talking to haybaler?
> > Is /var/dcc/ids correct, including permissions?
>
> ids on .201 never had a password for haybaler.  .201's map has always only 
> had localhost.

I'm confused about which IP addresses are on which hosts and which
numbers are network numbers and which are host numbers (e.g. 219 seems
to be both).  I can't see why 207.8.219.201 would send any DCC requests
to haybaler if the map file on 207.8.219.201 doesn't mention haybaler.
I also can't imagine haybaler inventing requests from 207.8.219.201
unless 207.8.219.201 has an entrey for haybaler in its map file.

Is the cause of the messages clear to you?  

I hope so, because I can't say anything coherent from my fog.


> > I'm chasing a bug in the new decoding of MIME multipart boundaries,
> > and hope to have 1.1.22 ready tonight or tomorrow.
>
> Yay :)

"yeah" is not exactly what I said when I found that dccproc and dccm
got different checksums for the same spam, except for the the carriage
returns that dccm saw but that sendmail stripped before it got to dccproc.


Vernon Schryver    vjs@rhyolite.com



More information about the DCC mailing list

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