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
|
<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>ClamSMTP: Using with Postfix</title>
<link rel="stylesheet" type="text/css" href="../../style.css">
</head>
<body bgcolor="#FFFFFF">
<h1>ClamSMTP: FAQ</h1>
<h3><a name="feature"/></a>Can you add XXX feature?</h3>
<p>Maybe, maybe not. But you should try and see if you can write a script
using the <tt>VirusAction</tt> feature (found in version 0.9 and later).
It allows you to run an arbitrary program whenever a virus is found.</p>
<h3><a name="clamd-error"/></a>Sometimes <tt>clamd</tt> uses up tons of CPU
and errors out on certain connections. How can I fix this?</h3>
<p>This should be fixed in versions later than 0.9. You may also want to
try upgrading your version of clamav. If it still occurs then let
<a href="mailto:clamsmtp-users@lists.sourceforge.net">the list</a> know.</p>
<h3><a name="zombie"></a>When I use the <tt>VirusAction</tt> option I see
defucnt or zombie processes left around. Why is that?</h3>
<p>When <tt>clamsmtpd</tt> runs the script it ignores it, and doesn't check
it's return value. This is done for efficiency. In some cases the SMTP
connection is complete before the <tt>VirusAction</tt> script completes. In
this case the process is left in the defunct/zombie state when it finishes.</p>
<p>Don't worry about this however, the process will be cleaned up the next
time a <tt>VirusAction</tt> is run. There should be at most one or two of
these processes hanging around.</p>
<h3><a name="timeout"/></a>I get an warning message saying that clamsmtpd couldn't
set timeouts on the connection.</h3>
<p>This occurs in with Linux kernels in the 2.2 series and earlier. Solutions
include upgrading to a later Linux version, or ignoring the warning.</p>
<h6>Copyright 2002, N. Nielsen [ <a href="./">clamsmtp</a> |
<a href="../../">home page</a> ]</h6>
</body>
</html>
|
