You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Matthias Leisi <ma...@leisi.net> on 2006/11/20 19:40:49 UTC

DNS Whitelist - rule optimization

I'd like to give SpamAssassin configuration instructions for the use of
dnswl.org (DNS Whitelisting project, see http://www.dnswl.org/). The
goal is to ensure a) efficient (minimal) use of DNS queries and b) that
fake headers do not trigger any whitelisting.

>From my understanding, this can be achieved by combining check_rbl(_sub)
with the "-firsttrusted" suffix. Is that correct (see
http://www.dnswl.org/tech.shtml)?

> header  RCVD_IN_DNSWL         eval:check_rbl('dnswl-firsttrusted', 'list.dnswl.org.')
> score   RCVD_IN_DNSWL         -0.1
> describe RCVD_IN_DNSWL        Received via whitelisted address, see http://www.dnswl.org/

The list returns different status codes depending on the
"trustworthiness" of an entry. Is the regex in check_rbl_sub the most
efficient way to differentiate the scores?

> header  RCVD_IN_DNSWL_LOW     eval:check_rbl_sub('dnswl-firsttrusted', '127.0.\d+.1')
> score   RCVD_IN_DNSWL_LOW     -1.0
> describe RCVD_IN_DNSWL_LOW    Reduce chance of false positive

Any additional considerations?

And a third and last point: Is it possible to add a dedicated header
when one of the rules triggered? I see that "add_header" can only
differentiate between spam, ham and all -- any additional options? The
idea is that MUAs could display something special for whitelisted mails
(eg Thunderbird with the Mnenhy extension).

Btw., if you want to give dnswl.org a try on your own system - please go
ahead, feedback is very welcome!

-- Matthias


Re: DNS Whitelist - rule optimization

Posted by Matthias Leisi <ma...@leisi.net>.

Theo Van Dinter wrote:

> My suggestion was going to be to have the plugin define tags that can
> be used via add_header.  No need for calling add_header() internally.

Sounds like an interesting idea. Since I've never written plugins for
SA: what is the best starting point / documentation?

>>> Btw., if you want to give dnswl.org a try on your own system - please go
>>> ahead, feedback is very welcome!
> 
> how is this different from other whitelist/accreditation systems?

It's different in that there is no business model associated with it, ie
it's not that some sender can "buy" it's way into the whitelist. Such
"buy in" models tend to be only used by senders with a shaddy reputation.

It's a collaborative effort since it relies for a good part on importing
and aggregating whitelisting data from various sources. Most likely,
many of you all maintain whitelists of largely overlapping senders (eg
banks), so it makes sense to share this data and maintain it
collaboratively.

There is a certain risk that a "bad sender" get's into the whitelist
through such collaboration. However once detected such a bad sender can
easily and swiftly be removed.

-- Matthias

Re: DNS Whitelist - rule optimization

Posted by Theo Van Dinter <fe...@apache.org>.
On Tue, Nov 21, 2006 at 03:21:12PM +0000, Justin Mason wrote:
> > And a third and last point: Is it possible to add a dedicated header
> > when one of the rules triggered? I see that "add_header" can only
> > differentiate between spam, ham and all -- any additional options? The
> > idea is that MUAs could display something special for whitelisted mails
> > (eg Thunderbird with the Mnenhy extension).
> 
> unfortunately, not without a plugin to call $pms->add_header().

I was originally going to respond with "what options would there be?"  The
options encapsulate all possible options, such as "all". ;)

My suggestion was going to be to have the plugin define tags that can
be used via add_header.  No need for calling add_header() internally.

> > Btw., if you want to give dnswl.org a try on your own system - please go
> > ahead, feedback is very welcome!

how is this different from other whitelist/accreditation systems?

-- 
Randomly Selected Tagline:
*'M ST*P*D - I'd like to buy a vowel Pat, an 'O'