Mailing List Archive: AOL And sa problems

AOL And sa problems

Feb 19, 2004, 8:44 AM

Post #1 of 4 (393 views)

Greetings,
Alot of e-mail coming from AOL.com addresses is being marked as spam.
When I check the reason why it says:

3.0 NO_RDNS_DOTCOM_HELO
and
1.9 FAKE_HELO_AOL

What are the reasons for this? As far as I can tell the helo doesn't
seem fake? And the reverse DNS does seem to match. Now not all of my
AOL incoming mail is being marked this way.. but alot of it is.

I'm running qmail with spamassassin 2.60

~ Matt

Re: AOL And sa problems [ In reply to ]

kelson at speed

Feb 19, 2004, 12:49 PM

Post #2 of 4 (392 views)

Permalink

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
SpeedGate Communications <www.speed.net>

RE: AOL And sa problems [ In reply to ]

gary at primeexalia

Feb 19, 2004, 1:12 PM

Post #3 of 4 (387 views)

Permalink

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:raquel@thericehouse.net]
Sent: Thu 2/19/2004 12:05 PM
To: spamassassin-users@incubator.apache.org
Cc:
Subject: Re: AOL And sa problems

On Thu, 19 Feb 2004 11:49:08 -0800
Kelson Vibber <kelson@speed.net> 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

RE: AOL And sa problems [ In reply to ]

qmail2 at chilitech

Feb 25, 2004, 6:21 AM

Post #4 of 4 (386 views)

Permalink

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:raquel@thericehouse.net]
> Sent: Thu 2/19/2004 12:05 PM
> To: spamassassin-users@incubator.apache.org
> Cc:
> Subject: Re: AOL And sa problems
>
>
>
> On Thu, 19 Feb 2004 11:49:08 -0800
> Kelson Vibber <kelson@speed.net> 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 <qmail2@chilitech.com>