• Regex Rule Numbering

    By Peter Gloor 2 decades ago

    After upgrading from kSPAM 1.4.2 to 1.6b2 I found some important good mails in the mail spam database.



    I looked into the document properties and found the following value in KS_REASON: "Subject: REGEX RULE:47"



    Looking for rule in document with rule #47 in the "By Rule Number" view of my configuration database, I found a regex rule (actually the first of all regex rules) that cannot be the cause for a match for that document.



    The closest rule, that eventually could be the cause for the problem, is rule #49.


    49 contains the following regex rule for the subject:

    REGEX#:(?i)([sß5$]{1,3}\W{0,2}[t]{1,3}\W{0,2}([o0]|(())){1,3}\W{0,2}[cz]{1,3}\W{0,2}[k]{1,3})



    If this rule fires if the subject contains the word "Aufstockung" then this is the reason for the problem.



    Now I have three questions:

    1. How are rule numbers counted in KS_REASON?
    2. Has anything in Regex changed since 1.4.2?
    3. How does a regex rule look that fires on "stock", but only if it stands as a word for itself

      a) at the beginning of the subject, or

      b) at the end of the subject, or

      c) inside the subject (preceded and followed by a space).



      Peter







      kSpam 1.6B2, Domino 6.0.3, Windows 2003 Server
    • Strange behaviour solved

      By Peter Gloor 2 decades ago

      After I deleted rule #49 and added it in a new document numbering and behaviour was o.k. again. I still have no explanation for this strange behaviour. I guess the document with rule #49 was corrupt in a way that influenced both, index and rule logic.



      When I started with 1.6b2 a number of other strange things happened I couldn't explain. Sometimes it looked like kSpam wouldn't respect my configuration settings. In addition users reported mails they received twice during rush hours.



      However, after the fix mentioned above and a fixup/compact on the databases normal behaviour returned.



      Now, about one month after the corrective actions everything still looks o.k. I have currently running 1.6b2 without problems for more than one month on two servers.



      Peter