Mailing-List: contact sysadmins-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Reply-To: sysadmins@spamassassin.apache.org
Date: Sun, 05 Nov 2017 13:49:11 -0500
User-Agent: K-9 Mail for Android
In-Reply-To: <ae479bef-a37b-92de-3963-6a02d3f21768@apache.org>
References: <4B09A9F4233E4D5FA705A36D5EDCE9AE@W2ADELLMERIJN> <1d4bc8a1-0ba2-43de-379b-accd8d6e1117@mcgrail.com> <dfb89cbc-a598-db27-92bc-71138f939d06@apache.org> <4c95c538d39a14774cc22f3da17669ae.squirrel@wuppie.web2all.nl> <a6bb4daf90977ce0aa6ddce4d6e113a5.squirrel@wuppie.web2all.nl> <ae479bef-a37b-92de-3963-6a02d3f21768@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----0FVYJ9IJFWE8M3D1A36L64B4OPELZT"
Content-Transfer-Encoding: 7bit
Subject: Re: mailspike in 72_scores
To: sysadmins@spamassassin.apache.org, Dave Jones <davej@apache.org>
From: "Kevin A. McGrail" <kevin.mcgrail@mcgrail.com>
Message-ID: <973BC351-5470-4CC7-A66D-902DFA190B33@mcgrail.com>
archived-at: Sun, 05 Nov 2017 18:49:22 -0000

------0FVYJ9IJFWE8M3D1A36L64B4OPELZT
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

You should rant about rspamd on list so you can shame moee into working on =
it :-)
Regards,
KAM

On November 5, 2017 12:21:03 PM EST, Dave Jones <davej@apache=2Eorg> wrote=
:
>On 11/05/2017 10:26 AM, Merijn van den Kroonenberg wrote:
>> Note to self: investigate why in do-nightly-rescore-example=2Esh is
>called
>> like this:
>> merge-scoresets $SCORESET
>> With a $SCORESET param=2E It will cause all rules which are not in that
>> scores-set$SCORESET file to be ignored and not written to the
>> 72_scores=2Ecf=2E
>>=20
>> The dos version of the script:
>>
>http://svn=2Eapache=2Eorg/repos/asf/spamassassin/trunk/rulesrc/sandbox/do=
s/new-rule-score-gen/do-nightly-rescore-example
>> Also has the $SCORESET param, but it does not seem to be set anywhere
>so
>> it might have functioned as if no param was given=2E
>>=20
>> To me it sounds illogical to ignore the net rules, they are just
>> masschecked less often, but should still be taken into consideration,
>> right?
>>=20
>>=20
>> And I just noticed: scores-set1 is still truncated at MILLION_USD,
>but
>> maybe  because the masscheck is only once a week?
>>=20
>>=20
>
>Not sure either=2E  I would like to get something to work even if it's
>not=20
>perfect so we can get sa-update updating again with "good enough"=20
>72_scores=2Ecf which would be better than nothing=2E  We can't roll out a=
ny
>
>new rules at all right now=2E
>
>Then I would love to carefully redesign the scripts so they could be
>run=20
>hourly instead of daily and only run if there is an actual
>change/commit=20
>waiting to be tested=2E  The new script would be more modular and share=
=20
>functions/logic instead of each one doing nearly identical things but=20
>slightly differently=2E  The scripts would have proper logging with=20
>meaningful return codes and not use "set -x" and "|| exit $?" which is=20
>extremely difficult to troubleshoot=2E
>
>Right now with the current problem of commits messing up the masscheck=20
>processing, it's taking days and weeks to troubleshoot problems as we=20
>make changes to try to improve things=2E  This makes the project seem
>like=20
>it's not doing anything when we are really trying hard to improve
>things=2E
>
>We need to add new features and improve SA or rspamd is going to take=20
>over and leave SA behind=2E  I have some ideas and plans that I would
>love=20
>to implement over time to help the entire SA install base but we have
>to=20
>have a solid foundation first=2E
>
>
>>>> Merijn,
>>>>
>>>> I am confused as to what is trying to be accomplished with the
>patch on
>>>> but 6400=2E  Maybe I am misunderstanding something=2E  It looks like
>these
>>>> MSPIKE scores need to remain in 50_scores=2Ecf since they are tied to
>a
>>>> specific SA version check > 3=2E4=2E0=2E
>>>
>>> Normally, all rules which are in 50_scores=2Ecf will never get
>rescored
>>> scores in 72_scores=2Ecf=2E
>>>
>>> The script to which the patch applies does this, but due to a too
>strict
>>> regex, it doesn't see any score line if its prepended with
>whitespace=2E
>>>
>>>>
>>>> Do we need to remove them from 72_scores=2Ecf, note that in the bug
>then
>>>> close it?
>>>
>>> Once the patch is applied, the mailspike rules should vanish from
>>> 72_scores=2Ecf by itself=2E
>>>
>>>>
>>>> Dave
>>>
>>>
>>=20
>>=20

------0FVYJ9IJFWE8M3D1A36L64B4OPELZT--