Qmail-LDAP
[Top] [All Lists]

Re: What is the different between /var/qmail/control/qmail-smtpd.rules a

To: qmail-ldap@qmail-ldap.org
Subject: Re: What is the different between /var/qmail/control/qmail-smtpd.rules and /service/smtpd/tcp?
From: "sato x" <gladiol4@gmail.com>
Date: Mon, 19 Mar 2007 10:57:41 +0700
Delivered-to: sp-com-lists@consult.net
Delivered-to: qmail-ldap-list@securepoint.com
Delivered-to: mailing list qmail-ldap@qmail-ldap.org
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=dJoKyLc2AY97wDR/8OY7uXK9wHhv205jmLH70v9p9EQVeLWmLS2LzHT5fbLQe82aOi0v9HgBhdc65Oq4wrHkxBdZRvLF6JvRNsTc5zCGUP+Rg8gXkVs6ebJpd3ehSF5+QmA+QA1INvduuDmuH8Bj1THUUbPUch9rPV2Uqc7Kwj8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VvhMTK74qexc9npmuC8SfGntjR2RNCYx/oxe6a1aN2vK+Y4mQvoC9SEK2daGZifJxBoEDzgilXAVMWAG8VUqyZ9sOoLIRujjhzxRqqrYD5r4dcNSUIZVCpkHmPeYYrqAbFZlne/qJVIpDzwmE/WTRr8bSwKFvslUeIGXe8J3ZsU=
In-reply-to: <20070316092502.GC74258@mail.webmonster.de>
Mailing-list: contact qmail-ldap-help@qmail-ldap.org; run by ezmlm
References: <f5ba7b270703160135k4aaf1828y607bab0b396ed820@mail.gmail.com> <20070316092502.GC74258@mail.webmonster.de>
Hi Sebastian,

As you know I am just a beginner in this qmail matters. So, I follow any tutorial in the net that I thought were reliable. I may fail sometimes, but they worth me a lot of learning that I finally know what should or should not be done.

Regarding tcp or qmail-smtpd.rules, I chose to utilize the qmail-smtpd.rules and it "half" work. The simscan was working, either spamassassin, but clamav was not (it did not scan email thoug I'd configured it in /etc/clamd.conf).  I can say that  because  the  header of the  email said
 
 Received: by simscan 1.1.0 ppid: 4019, pid: 4021, t: 8.1738s         scanners:none
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on    mail.domain2.co.id
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=ham    version=3.1.8

Now I've changed the user of simscan from clamav to simscan but it failed with

An error accured while sending email. The mail server responded: mail server temporarily rejected message (#4.3.0). Please check the message and try again.

I'll do some checking now. Thank you for your suggestion.

Best regards,

sato

On 3/16/07, Sebastian Benoit <benoit-lists@fb12.de> wrote:
sato x(gladiol4@gmail.com) on 2007.03.16 15:35:45 +0000:
> I want some explenation from people who understand the recipe of qmail-ldap
> about :

> 1. Does qmail-smtpd.rules replaces /service/smtpd/tcp? I mean, if there is a
> qmail-smtpd.rules in the control directory then qmail will utilize it instead
> of /service/smtpd/tcp. Which one should I choose: tcp or qmail-smtpd.rules?

The contents of /service/smtpd/tcp and qmail-smtpd.rules are stored in a cdb
database file using the 'tcprules' command like this:

  /usr/local/bin/tcprules tcp.cdb tcp.tmp < tcp

This file is then used by tcpserver in /service/smtpd/run:

  /usr/local/bin/tcpserver ... -xtcp.cdb ...

Which source file you use to create the tcp.cdb (or even if you name it that
or where you store it) is entirely dependend on your setup, your taste of
naming convention and what you like. The best thing to do ist to keep it
simple and consistent.

> 2. This time about simscan. I don't have a simscan user, instead I use clamav
> as the user when compile simscan-1.1 via
>    --enable-user=clamav
>    Is this OK?

It depends on the permissions that user already has, ie. which directories
are writeable by that user, etc.

When you install software like that the first time, its generally advisable
to follow the documentation and first learn how it works before playing
around with the installation procedure.

And you violate the principle of least surprise by running simscan as user
clamav...

/B.
--
Sebastian Benoit <benoit-lists@fb12.de >


<Prev in Thread] Current Thread [Next in Thread>