Jason Staudenmayer wrote: > > I upgrade from 2.63 to 3.1 a few weeks ago and it's running fine but I > can seem to figure out how to get something working again. > I did RTFM but I'm still at a loss, I'm looking to get my header > reports back in. below is what I have in my local.cf > > # This is the right place to customize your installation of > SpamAssassin. > # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be > # tweaked. > # > ######################################################################## > ### > # > #defang_mime 0 > > lock_method flock > > always_add_report 0 > > #report_header 1 > > #always_add_headers 1 > > add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ > tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ > > use_terse_report 0 > rewrite_subject 0 > report_safe 0 > required_hits 7.5 > > auto_whitelist_path /whitelist/auto-whitelist > auto_whitelist_file_mode 666 > auto_whitelist_factor 0.5 > > I know there are some old things still here but this is all I get in > the headers > > Processed in 3.636165 secs); 02 May 2006 09:58:55 -0000 > X-Spam-Status: Yes, hits=8.2 required=7.5 > > No report on what tests it hit on. > What I would like to see is the old terse report style headers
First, some generic advice. Run 'spamassassin --lint' and fix any errors that it finds. As for the headers, it looks like it is giving you what you asked for with your 'add_header' setting. It looks like it is really on two lines in your local.cf since what you got was just the first line of the status. Either put the entire 'add_header' definition on one line, or just remove it to get the default headers. -- Bowie
