https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6114

Adam Katz <apa...@khopis.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apa...@khopis.com

--- Comment #20 from Adam Katz <apa...@khopis.com> 2009-09-24 09:52:02 PDT ---
(In reply to comment #19)
> Perhaps we should consider a different way to handle SOUGHT and top200 on a
> daily basis.  It is a bit noisy to have daily svn commits, especially if we 
> add
> more daily rule channels.

Many of the elements of sc-neighbors change a bit each time (rather than just
top200, though that is likely the most dynamic of them), and the channel is
updated every few hours rather than every day.

One possible solution would be to have a separate SVN repository for the
automated lists.  That repository could be completely separate, or it could
sync with the main repo whenever somebody commits something by hand.  I'm also
willing to part with the generator's code if there's a better host (e.g. an SA
server tasked to this sort of thing).  I have an older version published on my
website, but I never cleaned up after adding the DNSBL crap to it, so it's a
mess at the moment.


(In reply to some talk on IRC, 2009-09-24 01:04 EDT)
> 01:04 < warren> khopesh: [24439] dbg: dns: query failed: 
>                 0.3.3.khop-sc-neighbors.sa.khopesh.com => NXDOMAIN
> 01:04 < warren> khopesh: your channels need to be updated for 3.3.0?

I consider it a common problem when channels just support ALL releases in one
blanket swoop.  It makes issues VERY hard to correct (especially given the lack
of expiration options -- now requested as bug 6210 -- which sc-neighbors SORELY
needs).  While this channel is almost certainly okay (though note the bottom
rules, which try to approximate DNSBL results if the implementation lacks
DNSEval ... bad things happen if SA changes its code to rename or replace
DNSEval), my other channels will remain available for 3.2.x only until an
official 3.3.0 Changelog hits.

> 12:36 < warren> khopesh: lots of people are using 3.3.0 already to validate
>                 it prior to release, and the official and SOUGHT channels
>                 already have 3.3.0 channels
> 12:37 < khopesh> is it in release candidacy?
> 12:37 < warren> pretty close, only need to rescore at this point

The re-score is part of the problem, since the bottom section of this channel
includes scores aimed to approximate the scores from RCVD_IN_BL_SPAMCOP_NET if
it is missing.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to