[ This is way overdue.  I've been a bit swamped to open a bug for it, though.
  And, as of version 2.20, I see that it's similar to the X-Spam-Level header,
  though an integer instead of asterisks.  Personally, this is more useful to
  me, using mh, and preferable to compare against. The patch included doesn't
  modify the tests in the t directory. ]

Justin,

I added the following feature to my local copy of spamassassin back in
January:

    o X-Spam-Hits header indicates the hits value for the mail message.

but have been a bit too busy lately to send a patch off to you.  So,
I'm quickly sending it off to you, in case it takes me a while to get
back to it.  [It took a while for me to get to it, afterall.  I'll
attempt to attach the patch after submitting this.]

I wanted something simple that I could use quickly with MH's scan
format to show the spamassassin hits value for each message.

This is just an old MH (or nmh) scan.default modified to display the
X-Spam-Hits value (after the patch below has been applied).

%5(msg)%<(cur)+%| %>%<{replied}-%?{encrypted}E%| %>\
%02(mon{date})/%02(mday{date})%<{date} %|*%>\
%<(mymbox{from})%<{to}To:%14(decode(addr{to}))%>%>\
%<(zero)%17(decode(addr{from}))%>  \
%<{x-spam-hits}%3(putnumf(compval{x-spam-hits}))%| %>  \
%(decode{subject})%<{body}<<%{body}>>%>

If the above is in "$HOME/`mhparam Path`/scan.spam", using
"scan -form scan.spam cur", one might see something like:

    1  03/04 1029912675861n13@   26  ****PROBABLY-SPAM**** Live life to the Ful

Of course, the "****PROBABLY-SPAM****" is a local config.  That
example message had a hits value of 26.2.  The X-Spam-Hits header
would look like:

X-Spam-Hits: 26.2

Just something that I thought would be useful for me to visually see
estimate spamassassin hit values in large amounts of mail, using my
regular MH tools. :)  (The main part of this came from wanting to verify
what spamassassin thought was spam versus my own view in archives.)
If MH's format files supported arbitrary parsing of subsections of headers,
I would've just pulled it from the X-Spam-Status header.

This was a quick hack.  So, I make no guarantees that it fits with
everything else nor is documented clearly. ;-)  The original patch was made
against spamassassin v2.01, but applied cleanly to v2.11.  The one attached
will be against v2.20.

I'm looking forward to getting back to playing with spamassassin.  Keep
up the good work.