Should dccproc always start dccifd?

We run dccd along with the dccm sendmail milter.  We also use dccproc
as a sendmail alias to report spam and feed it into an auto-reporter.
I noticed today that dccproc had started dccifd, even though we don't
use dccifd.  The man page does state that this will happen, for the
benefit of SpamAssassin.  We don't use that product either.

Here are the relevant sendmail log entries:

  May 28 17:08:58 electra dccproc[5556]: [ID 702911 mail.notice] try to start dccifd
  May 28 17:08:58 electra sm-mta[5551]: [ID 801593 mail.info] m4SM8u6o005506: to=|"/usr/local/bin/dccproc -R -t many | /usr/local/sbin/report-spam bin@cc.umanitoba.ca", ctladdr=<bin@cc.umanitoba.ca> (1/0), delay=00:00:02, xdelay=00:00:00, mailer=prog, pri=35253, dsn=2.0.0, stat=Sent

I assume this is harmless, but it raises a couple of questions.  Can
this be prevented?  Is there a more efficient way to handle these
spamtrap aliases?

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-