(Filed as a documentation bug, but perhaps better suited elsewhere...)

I had thought SYMBOLIC_TEST_NAME had to match /^(__)?[A-Z][A-Z_0-9]+$/ but there is a small number of rules that do not ... namely, rules in 20_freemail.cf (subrules only), 20_ratware.cf (subrules starting with __0), sandboxes emailed/00_FVGT_File001.cf (trailing lowercases), hege/20_hk.cf, hege/20_hk_dev.cf, and jm/80_sane.cf (trailing hashes using lowercase), plus many SARE rules and 72_active.cf has a hit (__FB_BCs) in updates.spamassassin.org (for 3.2.5) but not in subversion.

There does not appear to be a document stating what these can legally be nor are there suggestions aside from those pertaining to prefixing custom rules at http://wiki.apache.org/spamassassin/WritingRules#Rule_name_suggestions

http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Conf.html states that a description is best kept under 50 characters, but it never actually defines anything about what can and cannot be included in descriptions and SYMBOLIC_TEST_NAME.

Can symbolic test names be of any length and include any nonspace characters?  I'm doubting it...

Here's how I got a list as sorted by filename:

----
cd /path/to/spamassassin/svn/trunk

find * -name '*.cf' |xargs grep . |perl -ne 'if (/^(\S+):\s*(?:lang\s+\S+\s+)?(?:describe|score|tflags|priority|test|header|full|(?:raw)?body|meta|uri)\s+/) { my $file=$1; s///; s/\s.*//; print "$file: $_" unless /^(?:__)?[A-Z][A-Z_0-9]{1,50}$/; }' |sort |uniq

cd /var/lib/spamassassin/3.002005; !!
----


(It's amazing how much I've learned just by writing a syntax file for SA configs... see http://www.vim.org/scripts/script.php?script_id=2617 ... which I might want to check into svn once I get write access.)