From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Strange trouble with clamd/greylist/mimedefang
Date: Sat, 09 Jun 2007 17:49:08 +0000 [thread overview]
Message-ID: <466AE814.8010605@systella.fr> (raw)
Hello,
I use two UltraSparc workstations, the first one is an U80 named kant
(4*UII@450), the other one is an U60 named rayleigh (2*UII@450). kant is
a MX1 mail server that runs on debian testing sendmail, milter-greylist,
mimedefang with spamassassin and clamd. rayleigh is MX2.
On rayleigh, clamd and milter-greylist work fine. Some clamd process
and milter-greylist run at the same time, and this MX2 work.
rayleigh:[~] > ps auwx | grep milter
bertrand 3803 0.0 0.0 3520 976 pts/3 S+ 19:36 0:00 grep milter
root 23781 0.0 2.4 52144 24872 ? Ss Jun08 0:00
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
root 23782 0.0 2.4 52144 24872 ? S Jun08 0:00
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
root 23783 0.0 2.4 52144 24872 ? S Jun08 0:51
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
root 23784 0.0 2.4 52144 24872 ? S Jun08 0:00
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
root 23785 0.0 2.4 52144 24872 ? S Jun08 0:00
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
rayleigh:[~] > ps auwx | grep clamd
bertrand 3824 0.0 0.0 3520 976 pts/3 S+ 19:37 0:00 grep clamd
clamav 25331 1.0 7.6 86896 79376 ? Ss 15:19 2:39
/usr/sbin/clamd
clamav 26113 0.0 7.6 86896 79376 ? S 15:34 0:00
/usr/sbin/clamd
rayleigh:[~] >
With exactly the _same_ configuration, only one milter-greylist and one
clamd process run on kant !
kant:[~] > ps auwx | grep milter
root 9973 0.0 0.1 69968 2600 ? Ssl 19:16 0:00
/usr/local/bin/milter-greylist -P /var/run/greylist.pid -u root -p
/var/run/milter-greylist/greylist.sock
bertrand 12436 0.0 0.0 3800 1024 pts/1 S+ 19:37 0:00 grep milter
kant:[~] > ps auwx | grep clamd
clamav 5639 2.9 2.0 65936 42448 ? Ssl 19:06 0:55
/usr/sbin/clamd
bertrand 12467 0.0 0.0 3800 1024 pts/1 S+ 19:37 0:00 grep clamd
kant:[~] >
Some inbound mails are refused by kant (because clamd cannot scan all
inbound mails). They remain in sendmail DATA stage and SMTP transaction
aborts due to a timeout. I don't understand why with the same
configuration, MX1 does not works. I'm sure that clamd works fine on
rayleigh, but I'm not sure that it correctly works on kant. I don't see
any information on the logs and all sockets and permissions have been
verified. If I remove clamd support from mimedefang, kant works fine. I
don't understant why only one clamd process can run on kant.
Kernel is 2.6.20.11 (with netfilter ROUTE patch) from kernel.org.
Both run debian/testing. Kant is up to date. Last upgrade was made on
rayleigh 8 days ago.
Any idea ?
Regards,
JKB
next reply other threads:[~2007-06-09 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 17:49 BERTRAND Joël [this message]
2007-06-09 17:50 ` Strange trouble with clamd/greylist/mimedefang BERTRAND Joël
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466AE814.8010605@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.