Spamassassin reports

[Hugh Fraser]

The changes to add some additional info to the X-MailScanner-SpamCheck
header are quite simple, if changes the header rather than the message
itself suffices. I used a pipe created just before the fork() statement in
sendmail.pl to provide a connection to the child process, wrote back some
additional information to the parent (in my case, I wanted to know the
number of hits, the required number to be considered spam, and the list of
tests triggered by the mail) using the Mail::SpamAssassin::PerMsgStatus
object, in the same way the child currently gets the get_hits number. The
only twist is that the get_hits value is returned as the exit status of the
child process to the parent, and it's limited to a numeric value. Hence the
use of the pipe to pass arbitrary content back.