On Sat, Aug 23, 2003 at 10:38:35PM +1200, Simon Byrnand wrote: > Ok, I'll probably get thumped by someone for not RTFM but I'm just trying > out 2.60-rc2 on a test machine, and for whatever reason it is not adding > the X-Spam-Report header on messages that are detected as spam. > > Is there a new setting to disable this which is disabled by default ?
Sorta. With report_safe 0, the only way to get the report in the header is to also use "use_terse_report 1" (or since that's deprecated, "add_header spam Report _REPORT_"). I thought we documented that somewhere, but I can't seem to find it now. The basic idea was that with report_safe 1, there was no need to have the report in the header as well so it got disabled. For report_safe 0, the verbose report sucked, but setting "report_safe 0" didn't necessarily mean you wanted the terse report in the header. Hence the above behavior. > I've had a cursory look through the man pages but don't see anything > obvious, and I can't think why this default would be changed since 2.55, > so I'm wondering if this is a bug... The behavior isn't a bug, but it does need to be documented. Can you open a bugzilla ticket about this? We should add it to the report_safe doc. > Oh yeah, I'm talking about report_safe 0 mode too.... (which I suspect > doesn't get as much testing as report_safe 1 :) You'd be surprised. For instance, my personal box only does report_safe 0. :) -- Randomly Generated Tagline: The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first. (Arno Schaefer's .sig)
pgp00000.pgp
Description: PGP signature
