Mailing List Archive

RCVD_IN_DNSWL_HI Rule?
I'm curious about the DNSWL rule.  I have a brand new domain and just
created mail server for it.  I sent a test email to another one of my
servers which processes mail through SA.  On that test email on the
recipient side I get:

-5.0 RCVD_IN_DNSWL_HI       RBL: Sender listed at
https://www.dnswl.org/, high trust

I guess I should be honored that after only sending about 3 emails so
far from this domain, they like and trust my brand new domain so much
that I get a -5.0 credit for being so trustworthy. However, just a few
hours ago, I got an offer for beautiful russian girls that also got a
highly trusted rating and -5.0 credit which wiped out all of the other
SA rules' scores about it being spam.

I know nothing about this service.  But my personal opinion is that so
far for me, they don't have a very good track record about who they
trust.  I think a -5.0 score based on their result might require another
look.
Re: RCVD_IN_DNSWL_HI Rule? [ In reply to ]
On Tue, 4 Feb 2020 18:19:09 -0600
Jerry Malcolm wrote:

> I'm curious about the DNSWL rule.  I have a brand new domain and just
> created mail server for it.  I sent a test email to another one of my
> servers which processes mail through SA.  On that test email on the
> recipient side I get:
>
> -5.0 RCVD_IN_DNSWL_HI       RBL: Sender listed at
> https://www.dnswl.org/, high trust
>
> I guess I should be honored that after only sending about 3 emails so
> far from this domain,

It's nothing to do with your domain, it's the reputation of the first
trusted IP address.

> However, just a
> few hours ago, I got an offer for beautiful russian girls that also
> got a highly trusted rating and -5.0 credit which wiped out all of
> the other SA rules' scores about it being spam.
>
> I know nothing about this service.  But my personal opinion is that
> so far for me, they don't have a very good track record about who
> they trust.

I've never seem an FP at The 'HI' level, possibly this is a
configuration problem or a bug. IIWY I'd check what IP addresses
triggered it.