|
0
|
1 dccsight(8) Distributed Checksum Clearinghouse dccsight(8)
|
|
|
2
|
|
|
3 NNAAMMEE
|
|
|
4 ddccccssiigghhtt -- Distributed Checksum Clearinghouse raw checksum interface
|
|
|
5
|
|
|
6 SSYYNNOOPPSSIISS
|
|
|
7 ddccccssiigghhtt [--VVddQQCC] [--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]
|
|
|
8 [--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]
|
|
|
9
|
|
|
10 DDEESSCCRRIIPPTTIIOONN
|
|
|
11 DDccccssiigghhtt reads one or more lines containing DCC checksums, reports them
|
|
|
12 to a DCC server, and writes a X-DCC header line. It can be used to
|
|
|
13 report checksums obtained from dccproc(8) using --CC.
|
|
|
14
|
|
|
15 OOPPTTIIOONNSS
|
|
|
16 The following options are available:
|
|
|
17
|
|
|
18 --VV displays the version of the DCC raw checksum interface.
|
|
|
19
|
|
|
20 --dd enables debugging output from the DCC client software. Additional
|
|
|
21 --dd options increase the number of messages.
|
|
|
22
|
|
|
23 --QQ only queries the DCC server about the checksums instead of reporting
|
|
|
24 and then querying. This is useful when ddccccssiigghhtt is used to filter
|
|
|
25 mail that has already been reported to a DCC server by another DCC
|
|
|
26 client such as dccm(8). This can also be useful when applying a
|
|
|
27 private white or black list to mail that has already been reported
|
|
|
28 to a DCC server. No single mail message should be reported to a DCC
|
|
|
29 server more than once per recipient, such as would happen if
|
|
|
30 ddccccssiigghhtt is not given --QQ when processing a stream of mail that has
|
|
|
31 already been seen by a DCC client. Additional reports of a message
|
|
|
32 increase its apparent "bulkness."
|
|
|
33
|
|
|
34 --CC outputs the checksums for the message as well as the X-DCC header.
|
|
|
35
|
|
|
36 --hh _h_o_m_e_d_i_r
|
|
|
37 overrides the default DCC home directory, _/_v_a_r_/_d_c_c.
|
|
|
38
|
|
|
39 --mm _m_a_p
|
|
|
40 specifies a name or path of the memory mapped parameter file instead
|
|
|
41 of the default _m_a_p in the DCC home directory. It should be created
|
|
|
42 with the cdcc(8) command.
|
|
|
43
|
|
|
44 --ww _w_h_i_t_e_c_l_n_t
|
|
|
45 specifies an optional file containing SMTP client IP addresses and
|
|
|
46 SMTP headers of mail that do not need X-DCC headers and whose check-
|
|
|
47 sums should not be reported to the DCC server. It can also contain
|
|
|
48 checksums of spam. If the pathname is not absolute, it is relative
|
|
|
49 to the DCC home directory. Thus, individual users with private
|
|
|
50 whitelists usually specify them with absolute paths. It is useful
|
|
|
51 to _i_n_c_l_u_d_e a common or system-wide whitelist in private lists.
|
|
|
52
|
|
|
53 The format of the ddccccssiigghhtt whiteclnt file is the same as the
|
|
|
54 _w_h_i_t_e_l_i_s_t file required by dbclean(8) and dccsight(8). Because this
|
|
|
55 list is used frequently, a companion file is used. It has the same
|
|
|
56 pathname but with an added suffix of _._d_c_c_w. After being created
|
|
|
57 empty, it will contain an automatic memory mapped hash table of the
|
|
|
58 main file.
|
|
|
59
|
|
|
60 --tt _t_a_r_g_e_t_s
|
|
|
61 specifies the number of addressees of the message if other than 1.
|
|
|
62 The string _m_a_n_y instead of a number asserts that there were too many
|
|
|
63 addressees and that the message is unsolicited bulk email.
|
|
|
64
|
|
|
65 --ii _i_n_f_i_l_e
|
|
|
66 specifies an input file instead of standard input. If not absolute,
|
|
|
67 the pathname is interpreted relative to the directory in which
|
|
|
68 ddccccssiigghhtt was started.
|
|
|
69
|
|
|
70 --LL _l_t_y_p_e_,_f_a_c_i_l_i_t_y_._l_e_v_e_l
|
|
|
71 specifies how messages should be logged. _L_t_y_p_e must be _e_r_r_o_r, _i_n_f_o,
|
|
|
72 or _o_f_f to indicate which of the two types of messages are being con-
|
|
|
73 trolled or to turn off all syslog(3) messages from ddccccssiigghhtt. _L_e_v_e_l
|
|
|
74 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,
|
|
|
75 _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,
|
|
|
76 _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
|
|
|
77 through _L_O_C_A_L_7. The default is equivalent to
|
|
|
78 --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
|
|
|
79
|
|
|
80 ddccccssiigghhtt exits 0 on success, and >0 if an error occurs.
|
|
|
81
|
|
|
82 FFIILLEESS
|
|
|
83 /var/dcc DCC home directory in which other files are found.
|
|
|
84 map memory mapped file in the DCC home directory of information
|
|
|
85 concerning DCC servers.
|
|
|
86 whiteclnt contains the client whitelist in the format described in
|
|
|
87 dcc(8).
|
|
|
88 whiteclnt.dccw
|
|
|
89 memory mapped hash table of the _w_h_i_t_e_c_l_n_t file.
|
|
|
90
|
|
|
91 SSEEEE AALLSSOO
|
|
|
92 cdcc(8), dcc(8), dbclean(8), dccd(8), dblist(8), dccproc(8), dccm(8),
|
|
|
93 dccifd(8), mail(1), procmail(1).
|
|
|
94
|
|
|
95 HHIISSTTOORRYY
|
|
|
96 Implementation of ddccccssiigghhtt was started at Rhyolite Software in 2000.
|
|
|
97 This document describes version 1.3.103.
|
|
|
98
|
|
|
99 February 26, 2009
|
