Hi, > frontend servers at $DAYJOB and wondering > >> 1) if a SpamAssassin 3.4 release date is on the horizon >> 2) if not, is there anything useful a non-Perl-hacker can do to help >> accelerate that release date > >> 3) what advantages 3.4 has vs 3.3.2 and sa_update
I'm not sure if my questions are dev or user questions with how I've set up the latest svn snapshot, but hoped I could ask here. - Should the T_* rules be enabled? The 70_sandbox.cf config is part of the rules/ directory in the latest svn. Should that be omitted in production? - There are a lot of rules with no descriptions. Is this to be expected? dbg: config: warning: no description set for STOCK_PRICES dbg: config: warning: no description set for HK_LOTTO dbg: config: warning: no description set for TVD_PP_PHISH - There are a lot of failed dependency issues. dbg: rules: meta test KAM_BLANK01 has undefined dependency 'UNDISC_RECIPS' dbg: rules: meta test KAM_CARD has undefined dependency 'KAM_RPTR_SUSPECT' dbg: rules: meta test KAM_BLANK02 has undefined dependency 'MSGID_FROM_MTA_ID' dbg: rules: meta test KHOP_SC_CIDR8 has undefined dependency 'RCVD_IN_HOSTKARMA_WL' dbg: rules: meta test DHL_UPS_MISMATCH has undefined dependency '__FROM_DHL' I'm surprised RCVD_IN_HOSTKARMA_WL is no longer included? It looks to be in rulesrc/sandbox/wtogami/20_bug_6212_hostkarma.cf, but commented out. Thanks, Alex
