>> config: SpamAssassin failed to parse line, skipping: report_header 1
>
>> config: SpamAssassin failed to parse line, skipping: use_terse_report
>> 1
>
>> config: SpamAssassin failed to parse line, skipping: rewrite_subject
0
>
>> lint: 3 issues detected. please rerun with debug enabled for more
>> information.
>
>> Here are the local.cf settings:
>
>> report_safe 0
>
>> report_header 1
>
>> use_terse_report 1
>
>> rewrite_subject 0
>RDJ runs `spamassassin --lint` as part of the update process. The
>errors you reported were generated by SA as it scanned your local.cf.
>Basically, the error indicates that the three lines in your local.cf
are
>invalid. report_safe, report_header and rewrite_subject have not been
>valid configuration options for some time now.
>Looks like the local.cf was written to support SA 3.0.1 and you are
>currently running 3.0.4. Not sure when those options were deprecated
>but it's been a while. Current version of SA is 3.1.5.
>Check `man Mail::SpamAssassin::Conf` for details as to what the
>replacement options are.
Thanks Adam for the information. I have just pulled up a copy of the
man Mail::SpamAssassin::Conf. I cannot see where it details any
information on replacing these lines. I am continuing to search for
this information. Is there specific information I should look for? Any
additional direction on these settings in the local.cf would be
appreciated.
Sietse van Zanen [EMAIL PROTECTED] wrote:
rewrite_subject is nowadays
rewrite_header subject
I was able to comment out “report_header
1” and “use_terse_report 1” in the local.cf script. There
was already a line in the script “rewrite_header subject ***spam***”
in the local.cf file below the “rewrite_subject 0” line. I am
not sure why the “report_header 1” and “use_terse_report 1”
lines had been placed in the script but commenting them out did allow the
rules_du_jour script to run.
Thanks for the info.
Steve Ingraham
