|
0
|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
|
|
2 <HTML> |
|
|
3 <HEAD> |
|
|
4 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> |
|
|
5 <TITLE>dccproc.0.8</TITLE> |
|
|
6 <META http-equiv="Content-Style-Type" content="text/css"> |
|
|
7 <STYLE type="text/css"> |
|
|
8 BODY {background-color:white; color:black} |
|
|
9 ADDRESS {font-size:smaller} |
|
|
10 IMG.logo {width:6em; vertical-align:middle} |
|
|
11 </STYLE> |
|
|
12 </HEAD> |
|
|
13 <BODY> |
|
|
14 <PRE> |
|
|
15 <!-- Manpage converted by man2html 3.0.1 --> |
|
|
16 <B><A HREF="dccproc.html">dccproc(8)</A></B> Distributed Checksum Clearinghouse <B><A HREF="dccproc.html">dccproc(8)</A></B> |
|
|
17 |
|
|
18 |
|
|
19 </PRE> |
|
|
20 <H2><A NAME="NAME">NAME</A></H2><PRE> |
|
|
21 <B>dccproc</B> -- Distributed Checksum Clearinghouse Procmail Interface |
|
|
22 |
|
|
23 |
|
|
24 </PRE> |
|
|
25 <H2><A NAME="SYNOPSIS">SYNOPSIS</A></H2><PRE> |
|
|
26 <B>dccproc</B> [<B>-VdAQCHER</B>] [<B>-h</B> <I>homedir</I>] [<B>-m</B> <I>map</I>] [<B>-w</B> <I>whiteclnt</I>] [<B>-T</B> <I>tmpdir</I>] |
|
|
27 [<B>-a</B> <I>IP-address</I>] [<B>-f</B> <I>env</I><B>_</B><I>from</I>] [<B>-t</B> <I>targets</I>] [<B>-x</B> <I>exitcode</I>] |
|
|
28 [<B>-c</B> <I>type,</I>[<I>log-thold,</I>]<I>rej-thold</I>] [<B>-g</B> [<I>not-</I>]<I>type</I>] [<B>-S</B> <I>header</I>] |
|
|
29 [<B>-i</B> <I>infile</I>] [<B>-o</B> <I>outfile</I>] [<B>-l</B> <I>logdir</I>] [<B>-B</B> <I>dnsbl-option</I>] |
|
|
30 [<B>-L</B> <I>ltype,facility.level</I>] |
|
|
31 |
|
|
32 |
|
|
33 </PRE> |
|
|
34 <H2><A NAME="DESCRIPTION">DESCRIPTION</A></H2><PRE> |
|
|
35 <B>Dccproc</B> copies a complete SMTP message from standard input or a file to |
|
|
36 standard output or another file. As it copies the message, it computes |
|
|
37 the DCC checksums for the message, reports them to a DCC server, and adds |
|
|
38 a header line to the message. Another program such as <B>procmail(1)</B> can |
|
|
39 use the added header line to filter mail. Dccproc does not support any |
|
|
40 thresholds of its own, because equivalent effects can be achieved with |
|
|
41 regular expressions and you can apply dccproc several times using differ- |
|
|
42 ent DCC servers and then score mail based what all of the DCC servers |
|
|
43 say. |
|
|
44 |
|
|
45 Error messages are sent to stderr as well as the system log. Connect |
|
|
46 stderr and stdout to the same file to see errors in context, but direct |
|
|
47 stderr to /dev/null to keep DCC error messages out of the mail. The <B>-i</B> |
|
|
48 option can also be used to separate the error messages. |
|
|
49 |
|
|
50 <B>Dccproc</B> sends reports of checksums related to mail received by DCC |
|
|
51 clients and queries about the total number of reports of particular |
|
|
52 checksums. A DCC server receives no mail, address, headers, or other |
|
|
53 information, but only cryptographically secure checksums of such informa- |
|
|
54 tion. A DCC server cannot determine the text or other information that |
|
|
55 corresponds to the checksums it receives. It only acts as a clearing- |
|
|
56 house of counts of checksums computed by clients. |
|
|
57 |
|
|
58 For the sake of privacy for even the checksums of private mail, the |
|
|
59 checksums of senders of purely internal mail or other mail that is known |
|
|
60 to not be unsolicited bulk can be listed in a whitelist to not be |
|
|
61 reported to the DCC server. |
|
|
62 |
|
|
63 When <B>sendmail(8)</B> is used, <B><A HREF="dccm.html">dccm(8)</A></B> is a better DCC interface. <B><A HREF="dccifd.html">Dccifd(8)</A></B> |
|
|
64 is more efficient than <B>dccproc</B> because it is a daemon, but that has costs |
|
|
65 in complexity. See <B><A HREF="dccsight.html">dccsight(8)</A></B> for a way to use previously computed |
|
|
66 checksums. |
|
|
67 |
|
|
68 <A NAME="OPTIONS"><B>OPTIONS</B></A> |
|
|
69 The following options are available: |
|
|
70 |
|
|
71 <A NAME="OPTION-V"><B>-V</B></A> displays the version of the DCC <B>procmail(1)</B> interface. |
|
|
72 |
|
|
73 <A NAME="OPTION-d"><B>-d</B></A> enables debugging output from the DCC client software. Additional |
|
|
74 <B>-d</B> options increase the number of messages. One causes error mes- |
|
|
75 sages to be sent to STDERR as well as the system log. |
|
|
76 |
|
|
77 <A NAME="OPTION-A"><B>-A</B></A> adds to existing X-DCC headers (if any) of the brand of the current |
|
|
78 server instead of replacing existing headers. |
|
|
79 |
|
|
80 <A NAME="OPTION-Q"><B>-Q</B></A> only queries the DCC server about the checksums of messages instead |
|
|
81 of reporting and then querying. This is useful when <B>dccproc</B> is used |
|
|
82 to filter mail that has already been reported to a DCC server by |
|
|
83 another DCC client such as <B><A HREF="dccm.html">dccm(8)</A></B>. No single mail message should |
|
|
84 be reported to a DCC server more than once per recipient. |
|
|
85 |
|
|
86 It is better to use <I>MXDCC</I> lines in the <B>-w</B> <I>whiteclnt</I> file for your MX |
|
|
87 mail servers that use DCC than <B>-Q</B> |
|
|
88 |
|
|
89 <A NAME="OPTION-C"><B>-C</B></A> outputs only the X-DCC header and the checksums for the message. |
|
|
90 |
|
|
91 <A NAME="OPTION-H"><B>-H</B></A> outputs only the X-DCC header. |
|
|
92 |
|
|
93 <A NAME="OPTION-E"><B>-E</B></A> adds lines to the start of the log file turned on with <B>-l</B> and <B>-c</B> |
|
|
94 describing what might have been the envelope of the message. The |
|
|
95 information for the inferred envelope comes from arguments including |
|
|
96 <B>-a</B> and headers in the message when <B>-R</B> is used. No lines are gener- |
|
|
97 ated for which no information is available, such as the envelope |
|
|
98 recipient. |
|
|
99 |
|
|
100 <A NAME="OPTION-R"><B>-R</B></A> says the first Received lines have the standard |
|
|
101 "helo (name [address])..." format and the address is that of the |
|
|
102 SMTP client that would otherwise be provided with <B>-a</B>. The <B>-a</B> option |
|
|
103 should be used if the local SMTP server adds a Received line with |
|
|
104 some other format or does not add a Received line. Received headers |
|
|
105 specifying IP addresses marked <I>MX</I> or <I>MXDCC</I> in the <B>-w</B> <I>whiteclnt</I> file |
|
|
106 are skipped. |
|
|
107 |
|
|
108 <A NAME="OPTION-h"><B>-h</B></A> <I>homedir</I> |
|
|
109 overrides the default DCC home directory, <I>@prefix@</I>. |
|
|
110 |
|
|
111 <A NAME="OPTION-m"><B>-m</B></A> <I>map</I> |
|
|
112 specifies a name or path of the memory mapped parameter file instead |
|
|
113 of the default <I>map</I> in the DCC home directory. It should be created |
|
|
114 with the <B>new map</B> operation of the <B><A HREF="cdcc.html">cdcc(8)</A></B> command. |
|
|
115 |
|
|
116 <A NAME="OPTION-w"><B>-w</B></A> <I>whiteclnt</I> |
|
|
117 specifies an optional file containing SMTP client IP addresses and |
|
|
118 SMTP headers of mail that do not need X-DCC headers and whose check- |
|
|
119 sums should not be reported to the DCC server. It can also contain |
|
|
120 checksums of spam. If the pathname is not absolute, it is relative |
|
|
121 to the DCC home directory. Thus, individual users with private |
|
|
122 whitelists usually specify them with absolute paths. Common |
|
|
123 whitelists shared by users must be in the DCC home directory or one |
|
|
124 of its subdirectories and owned by the set-UID user of <B>dccproc</B>. It |
|
|
125 is useful to <I>include</I> a common or system-wide whitelist in private |
|
|
126 lists. |
|
|
127 |
|
|
128 Because the contents of the <I>whiteclnt</I> file are used frequently, a |
|
|
129 companion file is automatically created and maintained. It has the |
|
|
130 same pathname but with an added suffix of <I>.dccw</I>. It contains a mem- |
|
|
131 ory mapped hash table of the main file. |
|
|
132 |
|
|
133 <I>Option</I> lines can be used to modify many aspects of <B>dccproc</B> filter- |
|
|
134 ing, as described in the main <B><A HREF="dcc.html">dcc(8)</A></B> man page. For example, an |
|
|
135 <I>option</I> <I>spam-trap-accept</I> line turns off DCC filtering and reports the |
|
|
136 message as spam. |
|
|
137 |
|
|
138 <A NAME="OPTION-T"><B>-T</B></A> <I>tmpdir</I> |
|
|
139 changes the default directory for temporary files from the system |
|
|
140 default. The system default is <I>/tmp</I>. |
|
|
141 |
|
|
142 <A NAME="OPTION-a"><B>-a</B></A> <I>IP-address</I> |
|
|
143 specifies the IP address (not the host name) of the immediately pre- |
|
|
144 vious SMTP client. It is often not available. <B>-a</B> <I>0.0.0.0</I> is |
|
|
145 ignored. <B>-a</B>. The <B>-a</B> option should be used instead of <B>-R</B> if the |
|
|
146 local SMTP server adds a Received line with some other format or |
|
|
147 does not add a Received line. |
|
|
148 |
|
|
149 <A NAME="OPTION-f"><B>-f</B></A> <I>env</I><B>_</B><I>from</I> |
|
|
150 specifies the RFC 821 envelope "Mail From" value with which the mes- |
|
|
151 sage arrived. It is often not available. If <B>-f</B> is not present, the |
|
|
152 contents of the first Return-Path: or UNIX style From_ header is |
|
|
153 used. The <I>env</I><B>_</B><I>from</I> string is often but need not be bracketed with |
|
|
154 "<>". |
|
|
155 |
|
|
156 <A NAME="OPTION-t"><B>-t</B></A> <I>targets</I> |
|
|
157 specifies the number of addressees of the message if other than 1. |
|
|
158 The string <I>many</I> instead of a number asserts that there were too many |
|
|
159 addressees and that the message is unsolicited bulk email. |
|
|
160 |
|
|
161 <A NAME="OPTION-x"><B>-x</B></A> <I>exitcode</I> |
|
|
162 specifies the code or status with which <B>dccproc</B> exits if the <B>-c</B> |
|
|
163 thresholds are reached or the <B>-w</B> <I>whiteclnt</I> file blacklists the mes- |
|
|
164 sage. |
|
|
165 |
|
|
166 The default value is EX_NOUSER. EX_NOUSER is 67 on many systems. |
|
|
167 Use 0 to always exit successfully. |
|
|
168 |
|
|
169 <A NAME="OPTION-c"><B>-c</B></A> <I>type,</I>[<I>log-thold,</I>]<I>rej-thold</I> |
|
|
170 sets logging and "spam" thresholds for checksum <I>type</I>. The checksum |
|
|
171 types are <I>IP</I>, <I>env</I><B>_</B><I>From</I>, <I>From</I>, <I>Message-ID</I>, <I>substitute</I>, <I>Received</I>, |
|
|
172 <I>Body</I>, <I>Fuz1</I>, <I>Fuz2</I>, <I>rep-total</I>, and <I>rep</I>. The first six, <I>IP</I> through |
|
|
173 <I>substitute</I>, have no effect except when a local DCC server configured |
|
|
174 with <B>-K</B> is used. The <I>substitute</I> thresholds apply to the first sub- |
|
|
175 stitute heading encountered in the mail message. The string <I>ALL</I> |
|
|
176 sets thresholds for all types, but is unlikely to be useful except |
|
|
177 for setting logging thresholds. The string <I>CMN</I> specifies the com- |
|
|
178 monly used checksums <I>Body</I>, <I>Fuz1</I>, and <I>Fuz2</I>. <I>Rej-thold</I> and <I>log-thold</I> |
|
|
179 must be numbers, the string <I>NEVER</I>, or the string <I>MANY</I> indicating |
|
|
180 millions of targets. Counts from the DCC server as large as the |
|
|
181 threshold for any single type are taken as sufficient evidence that |
|
|
182 the message should be logged or rejected. |
|
|
183 |
|
|
184 <I>Log-thold</I> is the threshold at which messages are logged. It can be |
|
|
185 handy to log messages at a lower threshold to find solicited bulk |
|
|
186 mail sources such as mailing lists. If no logging threshold is set, |
|
|
187 only rejected mail and messages with complicated combinations of |
|
|
188 white and blacklisting are logged. Messages that reach at least one |
|
|
189 of their rejection thresholds are logged regardless of logging |
|
|
190 thresholds. |
|
|
191 |
|
|
192 <I>Rej-thold</I> is the threshold at which messages are considered "bulk," |
|
|
193 and so should be rejected or discarded if not whitelisted. |
|
|
194 |
|
|
195 DCC Reputation thresholds in the commercial version of the DCC are |
|
|
196 controlled by thresholds on checksum types <I>rep</I> and <I>rep-total</I>. Mes- |
|
|
197 sages from an IP address that the DCC database says has sent more |
|
|
198 than <B>-t</B> <I>rep-total,log-thold</I> messages are logged. A DCC Reputation |
|
|
199 is computed for messages received from IP addresses that have sent |
|
|
200 more than <B>-t</B> <I>rep-total,log-thold</I> messages. The DCC Reputation of an |
|
|
201 IP address is the percentage of its messages that have been detected |
|
|
202 as bulk or having at least 10 recipients. The defaults are equiva- |
|
|
203 lent to <B>-t</B> <I>rep,never</I> and <B>-t</B> <I>rep-total,never,20</I>. |
|
|
204 |
|
|
205 Bad DCC Reputations do not reject mail unless enabled by an <I>option</I> |
|
|
206 <I>DCC-rep-on</I> line in a <I>whiteclnt</I> file. |
|
|
207 |
|
|
208 The checksums of locally whitelisted messages are not checked with |
|
|
209 the DCC server and so only the number of targets of the current copy |
|
|
210 of a whitelisted message are compared against the thresholds. |
|
|
211 |
|
|
212 The default is <I>ALL,NEVER</I>, so that nothing is discarded, rejected, or |
|
|
213 logged. A common choice is <I>CMN,25,50</I> to reject or discard mail with |
|
|
214 common bodies except as overridden by the whitelist of the DCC |
|
|
215 server, the sendmail <I>${dcc</I><B>_</B><I>isspam}</I> and <I>${dcc</I><B>_</B><I>notspam}</I> macros, and |
|
|
216 <B>-g</B>, and <B>-w</B>. |
|
|
217 |
|
|
218 <A NAME="OPTION-g"><B>-g</B></A> [<I>not-</I>]<I>type</I> |
|
|
219 indicates that whitelisted, <I>OK</I> or <I>OK2</I>, counts from the DCC server |
|
|
220 for a type of checksum are to be believed. They should be ignored |
|
|
221 if prefixed with <I>not-</I>. <I>Type</I> is one of the same set of strings as |
|
|
222 for <B>-c</B>. Only <I>IP</I>, <I>env</I><B>_</B><I>From</I>, and <I>From</I> are likely choices. By default |
|
|
223 all three are honored, and hence the need for <I>not-</I>. |
|
|
224 |
|
|
225 <A NAME="OPTION-S"><B>-S</B></A> <I>hdr</I> |
|
|
226 adds to the list of substitute or locally chosen headers that are |
|
|
227 checked with the <B>-w</B> <I>whiteclnt</I> file and sent to the DCC server. The |
|
|
228 checksum of the last header of type <I>hdr</I> found in the message is |
|
|
229 checked. As many as 6 different substitute headers can be speci- |
|
|
230 fied, but only the checksum of the first of the 6 will be sent to |
|
|
231 the DCC server. |
|
|
232 |
|
|
233 <A NAME="OPTION-i"><B>-i</B></A> <I>infile</I> |
|
|
234 specifies an input file for the entire message instead of standard |
|
|
235 input. If not absolute, the pathname is interpreted relative to the |
|
|
236 directory in which <B>dccproc</B> was started. |
|
|
237 |
|
|
238 <A NAME="OPTION-o"><B>-o</B></A> <I>outfile</I> |
|
|
239 specifies an output file for the entire message including headers |
|
|
240 instead of standard output. If not absolute, the pathname is inter- |
|
|
241 preted relative to the directory in which <B>dccproc</B> was started. |
|
|
242 |
|
|
243 <A NAME="OPTION-l"><B>-l</B></A> <I>logdir</I> |
|
|
244 specifies a directory for copies of messages whose checksum target |
|
|
245 counts exceed <B>-c</B> thresholds. The format of each file is affected by |
|
|
246 <B>-E</B>. |
|
|
247 |
|
|
248 See the FILES section below concerning the contents of the files. |
|
|
249 See also the <I>option</I> <I>log-subdirectory-{day,hour,minute}</I> lines in |
|
|
250 <I>whiteclnt</I> files described in <B><A HREF="dcc.html">dcc(8)</A></B>. |
|
|
251 |
|
|
252 The directory is relative to the DCC home directory if it is not |
|
|
253 absolute |
|
|
254 |
|
|
255 <A NAME="OPTION-B"><B>-B</B></A> <I>dnsbl-option</I> |
|
|
256 enables DNS blacklist checks of the SMTP client IP address, SMTP |
|
|
257 envelope Mail_From sender domain name, and of host names in URLs in |
|
|
258 the message body. Body URL blacklisting has too many false posi- |
|
|
259 tives to use on abuse mailboxes. It is less effective than |
|
|
260 greylisting with <B><A HREF="dccm.html">dccm(8)</A></B> or <B><A HREF="dccifd.html">dccifd(8)</A></B> but can be useful in situa- |
|
|
261 tions where greylisting cannot be used. |
|
|
262 |
|
|
263 <I>Dnsbl-option</I> is either one of the <B>-B</B> <I>set:option</I> forms or |
|
|
264 <B>-B</B> <I>domain</I>[<I>,IPaddr</I>[<I>/xx</I>[<I>,bltype</I>]]] |
|
|
265 <I>Domain</I> is a DNS blacklist domain such as example.com that will be |
|
|
266 searched. <I>IPaddr</I>[<I>/xxx</I>] is the string "any" an IP address in the DNS |
|
|
267 blacklist that indicates that the mail message should be rejected, |
|
|
268 or a CIDR block covering results from the DNS blacklist. |
|
|
269 "127.0.0.2" is assumed if <I>IPaddr</I> is absent. IPv6 addresses can be |
|
|
270 specified with the usual colon (:) notation. Names can be used |
|
|
271 instead of numeric addresses. The type of DNS blacklist is speci- |
|
|
272 fied by <I>bltype</I> as <I>name</I>, <I>IPv4</I>, or <I>IPv6</I>. Given an envelope sender |
|
|
273 domain name or a domain name in a URL of spam.domain.org and a |
|
|
274 blacklist of type <I>name</I>, spam.domain.org.example.com will be tried. |
|
|
275 Blacklist types of <I>IPv4</I> and <I>IPv6</I> require that the domain name in a |
|
|
276 URL sender address be resolved into an IPv4 or IPv6 address. The |
|
|
277 address is then written as a reversed string of decimal octets to |
|
|
278 check the DNS blacklist, as in 2.0.0.127.example.com, |
|
|
279 |
|
|
280 More than one blacklist can be specified and blacklists can be |
|
|
281 grouped. All searching within a group is stopped at the first posi- |
|
|
282 tive result. |
|
|
283 |
|
|
284 Unlike <B><A HREF="dccm.html">dccm(8)</A></B> and <B><A HREF="dccifd.html">dccifd(8)</A></B>, no <I>option</I> <I>DNSBL-on</I> line is required in |
|
|
285 the <I>whiteclnt</I> file. A <B>-B</B> argument is sufficient to show that DNSBL |
|
|
286 filtering is wanted by the <B>dccproc</B> user. |
|
|
287 |
|
|
288 <B>-B</B> <I>set:no-client</I> |
|
|
289 says that SMTP client IP addresses and reverse DNS domain names |
|
|
290 should not be checked in the following blacklists. |
|
|
291 <B>-B</B> <I>set:client</I> restores the default for the following black- |
|
|
292 lists. |
|
|
293 |
|
|
294 <B>-B</B> <I>set:no-mail</I><B>_</B><I>host</I> |
|
|
295 says that SMTP envelope Mail_From sender domain names should |
|
|
296 not be checked in the following blacklists. <B>-B</B> <I>set:mail</I><B>_</B><I>host</I> |
|
|
297 restores the default. |
|
|
298 |
|
|
299 <B>-B</B> <I>set:no-URL</I> |
|
|
300 says that URLs in the message body should not be checked in the |
|
|
301 in the following blacklists. <B>-B</B> <I>set:URL</I> restores the default. |
|
|
302 |
|
|
303 <B>-B</B> <I>set:no-MX</I> |
|
|
304 says MX servers of sender Mail_From domain names and host names |
|
|
305 in URLs should not be checked in the following blacklists. |
|
|
306 <B>-B</B> <I>set:MX</I> restores the default. |
|
|
307 |
|
|
308 <B>-B</B> <I>set:no-NS</I> |
|
|
309 says DNS servers of sender Mail_From domain names and host |
|
|
310 names in URLs should not be checked in the following black- |
|
|
311 lists. <B>-B</B> <I>set:NS</I> restores the default. |
|
|
312 |
|
|
313 <B>-B</B> <I>set:defaults</I> |
|
|
314 is equivalent to all of <B>-B</B> <I>set:no-temp-fail</I> <B>-B</B> <I>set:client</I> |
|
|
315 <B>-B</B> <I>set:mail</I><B>_</B><I>host</I> <B>-B</B> <I>set:URL</I> <B>-B</B> <I>set:MX</I> and <B>-B</B> <I>set:NS</I> |
|
|
316 |
|
|
317 <B>-B</B> <I>set:group=X</I> |
|
|
318 adds later DNS blacklists specified with |
|
|
319 <B>-B</B> <I>domain</I>[<I>,IPaddr</I>[<I>/xx</I>[<I>,bltype</I>]]] |
|
|
320 to group 1, 2, or 3. |
|
|
321 |
|
|
322 <B>-B</B> <I>set:debug=X</I> |
|
|
323 sets the DNS blacklist logging level |
|
|
324 |
|
|
325 <B>-B</B> <I>set:msg-secs=S</I> |
|
|
326 limits <B>dccproc</B> to <I>S</I> seconds total for checking all DNS black- |
|
|
327 lists. The default is 25. |
|
|
328 |
|
|
329 <B>-B</B> <I>set:URL-secs=S</I> |
|
|
330 limits <B>dccproc</B> to at most <I>S</I> seconds resolving and checking any |
|
|
331 single URL. The default is 11. Some spam contains dozens of |
|
|
332 URLs and that some "spamvertised" URLs contain host names that |
|
|
333 need minutes to resolve. Busy mail systems cannot afford to |
|
|
334 spend minutes checking each incoming mail message. |
|
|
335 |
|
|
336 <A NAME="OPTION-L"><B>-L</B></A> <I>ltype,facility.level</I> |
|
|
337 specifies how messages should be logged. <I>Ltype</I> must be <I>error</I>, <I>info</I>, |
|
|
338 or <I>off</I> to indicate which of the two types of messages are being con- |
|
|
339 trolled or to turn off all <B>syslog(3)</B> messages from <B>dccproc</B>. <I>Level</I> |
|
|
340 must be a <B>syslog(3)</B> level among <I>EMERG</I>, <I>ALERT</I>, <I>CRIT</I>, <I>ERR</I>, <I>WARNING</I>, |
|
|
341 <I>NOTICE</I>, <I>INFO</I>, and <I>DEBUG</I>. <I>Facility</I> must be among <I>AUTH</I>, <I>AUTHPRIV</I>, |
|
|
342 <I>CRON</I>, <I>DAEMON</I>, <I>FTP</I>, <I>KERN</I>, <I>LPR</I>, <I>MAIL</I>, <I>NEWS</I>, <I>USER</I>, <I>UUCP</I>, and <I>LOCAL0</I> |
|
|
343 through <I>LOCAL7</I>. The default is equivalent to |
|
|
344 <B>-L</B> <I>info,MAIL.NOTICE</I> <B>-L</B> <I>error,MAIL.ERR</I> |
|
|
345 |
|
|
346 <B>dccproc</B> exits with 0 on success and with the <B>-x</B> value if the <B>-c</B> thresh- |
|
|
347 olds are reached or the <B>-w</B> <I>whiteclnt</I> file blacklists the message. If at |
|
|
348 all possible, the input mail message is output to standard output or the |
|
|
349 <A NAME="OPTION-o"><B>-o</B></A> <I>outfile</I> despite errors. If possible, error messages are put into the |
|
|
350 system log instead of being mixed with the output mail message. The exit |
|
|
351 status is zero for errors so that the mail message will not be rejected. |
|
|
352 |
|
|
353 If <B>dccproc</B> is run more than 500 times in fewer than 5000 seconds, <B>dccproc</B> |
|
|
354 tries to start <B><A HREF="dccifd.html">Dccifd(8)</A></B>. The attempt is made at most once per hour. |
|
|
355 Dccifd is significantly more efficient than <B>dccproc</B>. With luck, mecha- |
|
|
356 nisms such as SpamAssassin will notice when dccifd is running and switch |
|
|
357 to dccifd. |
|
|
358 |
|
|
359 |
|
|
360 </PRE> |
|
|
361 <H2><A NAME="FILES">FILES</A></H2><PRE> |
|
|
362 <A NAME="FILE-@prefix@">@prefix@</A> DCC home directory in which other files are found. |
|
|
363 <A NAME="FILE-map">map</A> memory mapped file in the DCC home directory of information |
|
|
364 concerning DCC servers. |
|
|
365 <A NAME="FILE-whiteclnt">whiteclnt</A> contains the client whitelist in the format described in |
|
|
366 <B><A HREF="dcc.html">dcc(8)</A></B>. |
|
|
367 <A NAME="FILE-whiteclnt.dccw">whiteclnt.dccw</A> |
|
|
368 is a memory mapped hash table corresponding to the <I>whiteclnt</I> |
|
|
369 file. |
|
|
370 <A NAME="FILE-tmpdir">tmpdir</A> contains temporary files created and deleted as <B>dccproc</B> pro- |
|
|
371 cesses the message. |
|
|
372 <A NAME="FILE-logdir">logdir</A> is an optional directory specified with <B>-l</B> and containing |
|
|
373 marked mail. Each file in the directory contains one message, |
|
|
374 at least one of whose checksums reached one of its <B>-c</B> thresh- |
|
|
375 olds. The entire body of the SMTP message including its |
|
|
376 header is followed by the checksums for the message. |
|
|
377 |
|
|
378 |
|
|
379 </PRE> |
|
|
380 <H2><A NAME="EXAMPLES">EXAMPLES</A></H2><PRE> |
|
|
381 The following <B>procmailrc(5)</B> rule adds an X-DCC header to passing mail |
|
|
382 |
|
|
383 :0 f |
|
|
384 | /usr/local/bin/dccproc -ERw whiteclnt |
|
|
385 |
|
|
386 This <B>procmailrc(5)</B> recipe rejects mail with total counts of 10 or larger |
|
|
387 for the commonly used checksums: |
|
|
388 |
|
|
389 :0 fW |
|
|
390 | /usr/local/bin/dccproc -ERw whiteclnt -ccmn,10 |
|
|
391 :0 e |
|
|
392 { |
|
|
393 EXITCODE=67 |
|
|
394 :0 |
|
|
395 /dev/null |
|
|
396 } |
|
|
397 |
|
|
398 |
|
|
399 </PRE> |
|
|
400 <H2><A NAME="SEE-ALSO">SEE ALSO</A></H2><PRE> |
|
|
401 <B><A HREF="cdcc.html">cdcc(8)</A></B>, <B><A HREF="dcc.html">dcc(8)</A></B>, <B><A HREF="dbclean.html">dbclean(8)</A></B>, <B><A HREF="dccd.html">dccd(8)</A></B>, <B><A HREF="dblist.html">dblist(8)</A></B>, <B><A HREF="dccifd.html">dccifd(8)</A></B>, <B><A HREF="dccm.html">dccm(8)</A></B>, |
|
|
402 <B><A HREF="dccsight.html">dccsight(8)</A></B>, <B>mail(1)</B>, <B>procmail(1)</B>. |
|
|
403 |
|
|
404 |
|
|
405 </PRE> |
|
|
406 <H2><A NAME="HISTORY">HISTORY</A></H2><PRE> |
|
|
407 Distributed Checksum Clearinghouses are based on an idea of Paul Vixie. |
|
|
408 Implementation of <B>dccproc</B> was started at Rhyolite Software in 2000. This |
|
|
409 document describes version 1.3.103. |
|
|
410 |
|
|
411 |
|
|
412 </PRE> |
|
|
413 <H2><A NAME="BUGS">BUGS</A></H2><PRE> |
|
|
414 <B>dccproc</B> uses <B>-c</B> where <B><A HREF="dccm.html">dccm(8)</A></B> uses <B>-t</B>. |
|
|
415 |
|
|
416 February 26, 2009 |
|
|
417 </PRE> |
|
|
418 <HR> |
|
|
419 <ADDRESS> |
|
|
420 Man(1) output converted with |
|
|
421 <a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a> |
|
|
422 modified for the DCC $Date 2001/04/29 03:22:18 $ |
|
|
423 <BR> |
|
|
424 <A HREF="http://www.dcc-servers.net/dcc/"> |
|
|
425 <IMG SRC="http://logos.dcc-servers.net/border.png" |
|
|
426 class=logo ALT="DCC logo"> |
|
|
427 </A> |
|
|
428 <A HREF="http://validator.w3.org/check?uri=referer"> |
|
|
429 <IMG class=logo ALT="Valid HTML 4.01 Strict" |
|
|
430 SRC="http://www.w3.org/Icons/valid-html401"> |
|
|
431 </A> |
|
|
432 </ADDRESS> |
|
|
433 </BODY> |
|
|
434 </HTML> |
