>> include /usr/local/etc/mail/spamassassin/rules.corvax/00_common-0.02.cf
>> include
>> /usr/local/etc/mail/spamassassin/rules.corvax/60_blist_header_from_real_name-0.04.cf
>>>> ...
>> /usr/local/etc/mail/spamassassin/rules.corvax/99_custom53-0.01.cf
>> ...
>> include
>> /usr/local/etc/mail/spamassassin/rules.corvax/99_report_headers-0.02.cf
>> а не проще не перегружать local.cf инклудами, а просто
> переместить/скопировать/создать симлинки на файлы правил рядом с local.cf?
а можно просто их положить в один из этих каталогов, откуда они сами и прочитаются
man spamassassin
Site-specific configuration data is used to override any values which had already been set.
This is loaded from the first existing directory in:
/etc/spamassassin
/usr/etc/mail/spamassassin
/usr/etc/spamassassin
/usr/local/etc/spamassassin
/usr/pkg/etc/spamassassin
/usr/etc/spamassassin
/etc/mail/spamassassin
/etc/spamassassin
From those three directories, SpamAssassin will first read files ending in ".pre" in lexical order and then
it will read files ending in ".cf" in lexical order (most files begin with two numbers to make the sorting
order obvious).
а при сработке правил в переменную _SUMMARY_ в report запишется причина?