On 2015-07-16 04:53, Kevin A. McGrail wrote:
You might find the regression_tests.cf in the trunk rules/ dir interesting. It's a way of giving strings you want to hit/not-hit on rules and see if it properly hits/doesn't hit as you expect. I also use mutt and a few macros such as one that run spamassassin -t 2>&1 with a prompt for a keyword. Helpful for debugging.
Can you elaborate on the macros any? After searching, I'm still having a hard time understanding conventional SA rule checking/debugging methods. I've been going my own route so far, but I would like to have a basic understanding how most folks do it. I'm not finding a much to get me started. (Guides on regression_tests.cf etc.)
Without knowing more at this point, do you think there may some usefulness to a tool that responds to keystrokes/keyphrases in real time like satester/rubular do? That is why I found the Rubular site so handy for checking my regex patterns in the first place and was inspired to write satester. For example, as I bang out a new rule, I can vary the sample text very quickly to check the pattern. Add/change/delete a character here or there and see what happens instantly. But with satester just on a larger scale. Sorry, not trying to spam my rule tool but just gain insight on where and if it is truly useful.
Anyway, a link or two for (basic|convention|intended) rule checking might be enough to get me started and more familiar with regular methods of checking/debugging.
Allen am -at- satester.com
