dccm, dccifd, dccproc comparison - comments?

Frank Bures fbures@chem.toronto.edu
Mon Jan 16 13:43:55 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For my own understanding I wrote a little dccm, dccifd and dccproc 
functionality comparison that follows.  Am I right in my assumptions?

dccproc:

Mail is piped to dccproc from procmail.  Dccproc adds X-DCC headers to mail 
and if '-c' criteria are met, exits with exit code 67.  Procmail recipes can 
be subsequently used to process such mail giving sysadmin full control over 
the filtering.  Greylisting does not work in dccproc.

dccifd and Spamassassin:

dccifd is fed mail by Mail::SpamAssassin::Plugin::DCC plugin to 
Spamassassin.
dccifd does not add any headers to the mail, but if '-t' criteria are met, 
the mail is flagged as spam by Spamassassin.  Outside of DCC's own controls 
(whitelist, blacklist etc.) user has no control over what is flagged as 
spam.  What I mean by this is that once the mail is flagged it cannot be 
unflagged without external tools.  Greylisting does not work in dccifd.

dccm:

Dccm is plugs into sendmail by milters.  It works at MTA level.  
Consequently any mail that meets '-t' criteria is rejected by sendmail 
directly and outside of DCC's own controls, uses has no way of accepting 
such mail.  Rejected mail cannot be "unrejected" at all.  Greylisting works 
in dccm.

Am I correct?  Any comments and enlightenment would be appreciated.

Thanks

Frank

Frank Bures, Dept. of Chemistry, University of Toronto, M5S 3H6
fbures@chem.toronto.edu
http://www.chem.utoronto.ca
PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=index&search=Frank+Bures
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0 OS/2 for non-commercial use
Comment: PGP 5.0 for OS/2
Charset: cp850

wj8DBQFDy5UL5kszaG0XLB4RAijTAKC7t1AK05UYP+fj2AM8+jdTPz9GowCeNZ4Y
pMXV4NiEHuAXNpWB2dTluIE=
=0g2C
-----END PGP SIGNATURE-----





More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.