We run 2 caching name servers here and still come up with these errors.
On Thu, 2004-02-19 at 15:12, Gary Smith wrote:
> Please note that this is only partially correct. A caching server on the
> localhost or your own local network should do. In our case we do not run DNS
> on the mail relay's as we have dedicated DNS servers for this.
>
> Gary Smith
>
> -----Original Message-----
> From: Raquel Rice [mailto:[EMAIL PROTECTED]
> Sent: Thu 2/19/2004 12:05 PM
> To: [EMAIL PROTECTED]
> Cc:
> Subject: Re: AOL And sa problems
>
>
>
> On Thu, 19 Feb 2004 11:49:08 -0800
> Kelson Vibber <[EMAIL PROTECTED]> wrote:
>
> > At 07:44 AM 2/19/2004, Matt wrote:
> > >3.0 NO_RDNS_DOTCOM_HELO
> > >and
> > >1.9 FAKE_HELO_AOL
> >
> > This was discussed a lot over the last few days. Consensus was
> > DNS timeouts. If you don't have one already, put a caching DNS
> > server on the same computer that's running SpamAssassin, and that
> > should stop or at least reduce the problem.
> >
> >
> > Kelson Vibber
>
> That could be why I'm not seeing any of those problems, I have a
> caching DNS server?
>
> --
> Raquel
> ============================================================
> The world acquires value only through its extremes and endures only
> through moderation; extremists make the world great, the moderates
> give it stability.
> --Paul Valery
>
>
--
Matt <[EMAIL PROTECTED]>
