Re: Filtering Header Draft Discussion

Philip Miller wrote:
> If you can't or
> don't want to discuss this in Jabber, but have thoughts, please email 
> them to the
> Filtering Subgroup list.

When reading headers, I prefer to see them concise, self-explanatory,
and most importantly, easy for both humans and programs to parse.  The
format used by SpamAssassin and Bogofilter seem to meet these
requirements, so I adopted them for my own filters.  For example, I
have a general DNSBL filter that allows users to check any DNSBL they
wish.  Example header:

X-DNSBL: 219.146.207.114, dnsbl.njabl.org=127.0.0.9

Ditto for a general RHSBL filter:

X-RHSBL: 01o.com, rhsbl.ahbl.org=127.0.0.2

After reading the draft, I see the X-DNSBL entry looking something like:

X-DNSBL: ip="219.146.207.114"; dnsbl="dnsbl.njabl.org"; value="127.0.0.9";

I don't see any problems with making these changes.

Does anyone have a feel for how much effort is being put into client-
side filtering?  I'm curious to know what's driving the standard and
who needs what where.

-- 
Jack Bailey