The only changes that I made to whiteclnt relative to the original
are:
mxdcc ip 137.145.210.56
and
env_to postmaster@colby.edu
137.145.210.56 is our lowest MX and our mail server. It is the
box that runs dccifd, as well as sendmail, MailScanner, SpamAssassin,
and a stealth copy of bind for local DNS service.
I did used to have "ok ip 137.146.0.0/16" in the file, but after
some spambots in the dorms, I no longer trust my own netblock. :)
Jeff Earickson
Colby College
On Wed, 7 Dec 2005, Vernon Schryver wrote:
> Date: Wed, 7 Dec 2005 12:32:49 -0700 (MST)
> From: Vernon Schryver <vjs@calcite.rhyolite.com>
> To: dcc@calcite.rhyolite.com> Subject: Re: spamassassin/dccifd: write(MTA socket,XX): Broken pipe
>>> From: "Jeff A. Earickson"
>>> I added "dcc_timeout 10" to my spam.assassin.prefs.conf in my
>> MailScanner/etc directory (MS 4.47.4, Solaris 9). It seems to
>> have reduced the number of broken pipe messages, but...
>> I should mention another possible trigger for dccifd being slow
> arbitrarily slow. If you use host names in /var/dcc/whiteclnt
> and if /var/dcc/whiteclnt.dccw is invalid, then dccifd cannot
> use a separate thread to resolve those host names. The whole
> thing must stop until your local DNS resolver library gives answers.
>>> Vernon Schryver vjs@rhyolite.com> _______________________________________________
> DCC mailing list DCC@rhyolite.com>http://www.rhyolite.com/mailman/listinfo/dcc>