At 05:09 AM 10/24/2007, cpayne wrote:
Hey Guys,
Got a problem, I been looking on the net no clear answer. But why
can't I use this have they change....
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line,
skipping, in "/etc/mail/spamassassin/local.cf": pyzor_add_header 1
Oct 24 08:02:45 magi spamd[2942]: config: failed to parse line,
skipping, in "/etc/mail/spamassassin/local.cf": use_terse_report 1
Any help you can give.
Did you just upgrade?
Googling pyzor_add_header and use_terse_report show quite a few answers:
http://spamassassinbook.packtpub.com/chapter11_preview.htm
Versions of SpamAssassin before 3.0 used the pyzor_add_header
configuration directive to add a header to emails. This has been
deprecated, and will be removed in future versions of SpamAssassin.
The current method is to add an email header with Pyzor information.
This is achieved by adding the following to
/etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs:
add_header all Pyzor _PYZOR_
and googling use_terse_report, the first google hit:
http://www.hoboes.com/Mimsy/?ART=201
The use_terse_report rule has also changed in SpamAssassin 3. I
couldn't find the replacement, but thanks to Wolfgang from Vienna, I
now know the answer:
remove_header all Report
This doesn't switch from a detailed to a terse report header; it
removes the detailed report completely. But (as I understand it) in
SpamAssassin 3, the terse and detailed reports have been separated
out into X-Spam-Status (the terse version) and X-Spam-Report (the
detailed version). Removing the detailed version leaves just the terse version.
