Here's an interesting note in advance for all the rule creators reading
the list. I decided to test out the new 3.0 cvs code to see if it would
behave on a test server I'm working on. In addition to requiring some
basic configuration options being renamed or set up a bit differently, I
discovered that when I lint my ruleset I get a massively long list of
warning messages. most of them read like:
warning: description for FVGT_s_OBFU_V is over 50 chars
warning: description for T_RATWARE_OOPS_11 is over 50 chars
or
warning: score set for non-existent rule RCVD_IN_EFIVETEN
or
warning: rule 'LOCAL_DRUGS_MALEDYSFUNCTION' is over 22 chars
I'm assuming that everything else loaded up right, and my scores seem
to be comparable in general on first glance. Also, there seems to be a
speed improvement on spamd noticeable.
That's it. Just thought it was interesting, and everybody writing or
describing rules might want to parse their sets to make sure they fall
within the boundaries of 50 or 22 characters that seem to be more mandatory.
Ben
the list. I decided to test out the new 3.0 cvs code to see if it would
behave on a test server I'm working on. In addition to requiring some
basic configuration options being renamed or set up a bit differently, I
discovered that when I lint my ruleset I get a massively long list of
warning messages. most of them read like:
warning: description for FVGT_s_OBFU_V is over 50 chars
warning: description for T_RATWARE_OOPS_11 is over 50 chars
or
warning: score set for non-existent rule RCVD_IN_EFIVETEN
or
warning: rule 'LOCAL_DRUGS_MALEDYSFUNCTION' is over 22 chars
I'm assuming that everything else loaded up right, and my scores seem
to be comparable in general on first glance. Also, there seems to be a
speed improvement on spamd noticeable.
That's it. Just thought it was interesting, and everybody writing or
describing rules might want to parse their sets to make sure they fall
within the boundaries of 50 or 22 characters that seem to be more mandatory.
Ben