spamass-milter 0.20 + Sendmail 8.12.10 + SpamAssassin 2.60, headers not added, but bodies can be replaced?

[Jay Libove]

I just built SpamAssassin 2.60 to go with Sendmail 8.12.10 on an
approximately RedHat 9 system (GCC 3.22 2030222 [RedHat Linux 3.2.2-5],
PERL 5.8.0 [with LANG=en_US to get rid of the UTF8 bug]) and
spamass-milter 0.20.

If I configure SpamAssassin with "report_safe 1" to replace the whole
message with a SpamAssassin munged report and the original message
attached, it works fine.

However, I prefer to use SpamAssassin the mode documented for
"report_safe 0" where SpamAssassin will only add/change headers, but not
otherwise modify the message body. When I configure SpamAssassin this way,
however, no modifications occur at all to the messages, even though the
debug logs show that SpamAssassin declared a message to be spam and claims
to have added a variety of X-Spam* headers.

Any suggestions please on what might be incompatible on my system, or
configured wrong, or known bugs/workarounds, &etc?

Thanks!
-Jay

/etc/mail/spamassassin/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.
#
###########################################################################
#
rewrite_subject 0
report_safe 1
# just put X-Spam* headers in, don't rewrite the whole
# message attaching the original (as "1" would do)
# report_safe 0
trusted_networks 209.124.85.240/28
auto_whitelist_path /usr4/spamd/auto_whitelist_file
bayes_path /usr4/spamd/bayes


spamd command line from /etc/rc.d/init.d/spamd:
spamd -d -a -m5 -H /usr4/spamd -D


relevant bits from sendmail.cf:
Xspamassassin, S=local:/var/run/spamass.sock, F=, T=C:15m;S:1m;R:1m;E:2m
O InputMailFilters=spamassassin


spamass-milter command line:
spamass-milter -p /var/run/spamass.sock -f -d 1,spamc