File: dccsight.0

package info (click to toggle)
dcc 1.2.74-2
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 3,552 kB
  • ctags: 4,041
  • sloc: ansic: 41,034; perl: 2,310; sh: 2,186; makefile: 224
file content (97 lines) | stat: -rw-r--r-- 5,488 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
dccsight(8)           Distributed Checksum Clearinghouse           dccsight(8)

NNAAMMEE
     ddccccssiigghhtt -- Distributed Checksum Clearinghouse raw checksum interface

SSYYNNOOPPSSIISS
     ddccccssiigghhtt [--VVddQQ] [--hh _h_o_m_e_d_i_r] [--mm _m_a_p] [--ww _w_h_i_t_e_c_l_n_t] [--aa _I_P_-_a_d_d_r_e_s_s]
              [--ff _e_n_v___f_r_o_m] [--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
     report checksums obtained from dccproc(8) using --CC.

   OOPPTTIIOONNSS
     The following options are available:

     --VV   displays the version of the DCC raw checksum interface.

     --dd   enables debugging output from the DCC client library.  Additional --dd
          options increase the number of messages.

     --QQ   only queries the DCC server about the checksums instead of reporting
          and then querying.  This is useful when ddccccssiigghhtt is used to filter
          mail that has already been reported to a DCC server by another DCC
          client such as dccm(8).  This can also be useful when applying a
          private white or black list to mail that has already been reported
          to a DCC server.  No single mail message should be reported to a DCC
          server more than once per recipient, such as would happen if
          ddccccssiigghhtt is not given --QQ when processing a stream of mail that has
          already been seen by a DCC client.  Additional reports of a message
          increase its apparent "bulkness."

     --hh _h_o_m_e_d_i_r
          overrides the default DCC home directory, which is often /var/dcc.

     --mm _m_a_p
          specifies a name or path of the memory mapped parameter file instead
          of the default _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
          _w_h_i_t_e_l_i_s_t file required by dbclean(8) and dccsight(8).  Because 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 being 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 or
          _i_n_f_o to indicate which of the two types of messages are being con-
          trolled.  _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
     /var/dcc   DCC home directory in which other files are found.
     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 _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 describes version 1.2.74.

FreeBSD 4.9                     March 20, 2005                     FreeBSD 4.9