dccsight(8) FreeBSD System Manager's Manual dccsight(8) NNAAMMEE ddccccssiigghhtt -- Distributed Checksum Clearinghouse raw checksum interface SSYYNNOOPPSSIISS ddccccssiigghhtt [--VVddPPQQCC] [--hh _h_o_m_e_d_i_r] [--mm _m_a_p] [--ww _w_h_i_t_e_c_l_n_t] [--tt _t_a_r_g_e_t_s] [--ii _i_n_f_i_l_e] [--LL _l_t_y_p_e_,_f_a_c_i_l_i_t_y_._l_e_v_e_l] DDEESSCCRRIIPPTTIIOONN DDccccssiigghhtt reads one or more lines containing DCC checksums, reports them to a DCC server, and writes a X-DCC header line. It can be used to re- port checksums obtained from dccproc(8) using --CC. OOPPTTIIOONNSS The following options are available: --VV displays the version of the DCC raw checksum interface. Two or more --VV options show the options with which it was built. --dd enables debugging output from the DCC client software. Additional --dd options increase the number of messages. --PP The SpamAsassin DCC.pm plugin should watch for "bulk" in X-DCC SMTP header fields, but historically has looked for counts of "many". However, there are situations when ddccccssiigghhtt knows that a mail mes- sage is extremely bulky and probably spam. For example, mail from a sender that is blacklisted in _w_h_i_t_e_c_l_n_t gets an X-DCC header that includes _b_u_l_k. To acommodate that bug in SpamAssassin, by default whenever ddccccssiigghhtt generates an X-DCC header containing "bulk", it also forces the _B_o_d_y count to "many". --PP turns off that kludge and the _B_o_d_y contains the count from the DCC server. --QQ only queries the DCC server about the checksums of messages instead of reporting. This is useful when ddccccssiigghhtt is used to filter mail that has already been reported to a DCC server by another DCC client. No single mail message should be reported to a DCC server more than once per recipient, because each report will increase the apparent "bulkness" of the message. It is better to use _M_X_D_C_C lines in the global _/_v_a_r_/_d_c_c_/_w_h_i_t_e_c_l_n_t file for your MX mail servers that use DCC than to use --QQ with ddccccssiigghhtt. Do not use --QQ except on mail that you know has been reported to a DCC server. DCC depends on reports of all except known private mail and works only because almost no DCC installations use --QQ. --CC outputs the checksums for the message as well as the X-DCC header. --hh _h_o_m_e_d_i_r overrides the default DCC home directory, _/_v_a_r_/_d_c_c. --mm _m_a_p specifies a name or path of the memory mapped parameter file instead of the default _/_v_a_r_/_d_c_c_/_m_a_p in the DCC home directory. It should be created with the cdcc(8) command. --ww _w_h_i_t_e_c_l_n_t specifies an optional file containing SMTP client IP addresses and SMTP headers of mail that do not need X-DCC headers and whose check- sums should not be reported to the DCC server. It can also contain checksums of spam. If the pathname is not absolute, it is relative to the DCC home directory. Thus, individual users with private whitelists usually specify them with absolute paths. It is useful to _i_n_c_l_u_d_e a common or system-wide whitelist in private lists. The format of the ddccccssiigghhtt whiteclnt file is the same as the _/_v_a_r_/_d_c_c_/_w_h_i_t_e_l_i_s_t file required by dbclean(8) and dccsight(8). Be- cause this list is used frequently, a companion file is used. It has the same pathname but with an added suffix of _._d_c_c_w. After be- ing created empty, it will contain an automatic memory mapped hash table of the main file. --tt _t_a_r_g_e_t_s specifies the number of addressees of the message if other than 1. The string _m_a_n_y instead of a number asserts that there were too many addressees and that the message is unsolicited bulk email. --ii _i_n_f_i_l_e specifies an input file instead of standard input. If not absolute, the pathname is interpreted relative to the directory in which ddccccssiigghhtt was started. --LL _l_t_y_p_e_,_f_a_c_i_l_i_t_y_._l_e_v_e_l specifies how messages should be logged. _L_t_y_p_e must be _e_r_r_o_r, _i_n_f_o, or _o_f_f to indicate which of the two types of messages are being con- trolled or to turn off all syslog(3) messages from ddccccssiigghhtt. _L_e_v_e_l must be a syslog(3) level among _E_M_E_R_G, _A_L_E_R_T, _C_R_I_T, _E_R_R, _W_A_R_N_I_N_G, _N_O_T_I_C_E, _I_N_F_O, and _D_E_B_U_G. _F_a_c_i_l_i_t_y must be among _A_U_T_H, _A_U_T_H_P_R_I_V, _C_R_O_N, _D_A_E_M_O_N, _F_T_P, _K_E_R_N, _L_P_R, _M_A_I_L, _N_E_W_S, _U_S_E_R, _U_U_C_P, and _L_O_C_A_L_0 through _L_O_C_A_L_7. The default is equivalent to --LL _i_n_f_o_,_M_A_I_L_._N_O_T_I_C_E --LL _e_r_r_o_r_,_M_A_I_L_._E_R_R ddccccssiigghhtt exits 0 on success, and >0 if an error occurs. FFIILLEESS @prefix@ DCC home directory. map memory mapped file in the DCC home directory of information concerning DCC servers. whiteclnt contains the client whitelist in the format described in dcc(8). whiteclnt.dccw memory mapped hash table of the _/_v_a_r_/_d_c_c_/_w_h_i_t_e_c_l_n_t file. SSEEEE AALLSSOO cdcc(8), dcc(8), dbclean(8), dccd(8), dblist(8), dccproc(8), dccm(8), dccifd(8), mail(1), procmail(1). HHIISSTTOORRYY Implementation of ddccccssiigghhtt was started at Rhyolite Software in 2000. This document describes version RHYOLITE_VERSION. March 22, 2024