In case anyone else uses a script to scan the SA injected message headers
to build log records (to detail matched tests, etc), and that script cares
about the *order* of the headers, then please take note that in 3.3.1 the
position of the 'report_safe 0' command in your .cf files relative to the
add_header command(s) determines the position in which X-Spam-Report will
appear in the headers, relative to the others.
This is a minor difference from 3.2.5 - strictly speaking it gives 3.3.1
superior behaviour, with more control/flexibility. So no complaints. :)
Just wanted to mention this in case anyone else notes anomalies in
their custom logging....
- Charles
