Qmail-LDAP
[Top] [All Lists]

Re: qmail-ldap installation FAILURE again and again and .....

To: "Sameer N Ingole" <strike@proscrutiny.com>
Subject: Re: qmail-ldap installation FAILURE again and again and .....
From: "sato x" <gladiol4@gmail.com>
Date: Thu, 1 Mar 2007 20:38:57 +0700
Cc: qmail-ldap@qmail-ldap.org
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:cc:in-reply-to:mime-version:content-type:references; b=h3fJnrlmfSY8PLSvGQ8r1ZhLsdygCD7v3KGrP4Ocswq8mzm1H+T6QilAY+KKFrulld3a1LkCiCidLsm3EmDXKDAbL8lq/foA9aX7ZRZnF9GD1lBtka8hpZdBuAOYALLaz1ZSK6uyJFTreKS/cm/sapR7RayoKzUhLpFl8RNjhZ8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=KPyNVg2P5D+PMpN6HaiW2d5xJf3v1Tv2AEH1NDo9dYvLi3ruzeJSFq3XKheqzsx+5NMzVZYN9byVAvhvU8LcAO6mShypKS/SVOnYB/Wyg+iCunRUP6ZbCBJEqDDAKOyGCfin1G/cnw6xWZ7NDxb11dS9DGlUFv+YR8LX5oV1ukc=
In-reply-to: <45E6B116.6080704@proscrutiny.com>
Mailing-list: contact qmail-ldap-help@qmail-ldap.org; run by ezmlm
References: <f5ba7b270702271958x60fc5d0u1bf188440188bc3@mail.gmail.com> <f5ba7b270702280348i4b34ac7axffa1793d96e53802@mail.gmail.com> <20070228122545.GB8752@diehard.n-r-g.com> <f5ba7b270702281904k3adca764u766d815fde19c850@mail.gmail.com> <45E664E6.9050408@proscrutiny.com> <f5ba7b270702282301o6f275bb5rcc45c125519557c9@mail.gmail.com> <45E68539.8060903@proscrutiny.com> <f5ba7b270703010209o746b9727gfa37664d3a2ba171@mail.gmail.com> <45E6AE5B.9010008@proscrutiny.com> <45E6B116.6080704@proscrutiny.com>
Hi...
I've included HDIRMAKE and make setup check again. Here is what I get from running telnet localhost at port 25

[root@mail qmail-smtpd]# env LOGLEVEL=255 ./run
tcpserver: status: 0/50
tcpserver: status: 1/50
tcpserver: pid 3441 from 127.0.0.1
tcpserver: ok 3441 mail.domain.co.id:127.0.0.1:25 localhost:127.0.0.1::32783
pbscheck unable to read controls
tcpserver: end 3441 status 256
tcpserver: status: 0/50

and in /var/qmail/service/qmail/log/main/current

@4000000045e6b24c186e2c5c delivery 7: deferral: \ Unable_to_login_into_LDAP_server,_bad_credentials._(#4.4.3)/
@4000000045e6b24c186e43cc status: local 0/10 remote 0/20
@4000000045e6b8f009071a94 starting delivery 8: msg 2062953 to local \ sato.br@domain.co.id @4000000045e6b8f009073204 status: local 1/10 remote 0/20

 [root@mail qmail]# cat ./service/pop3d/log/main/current
@4000000045e6c0812ac1ee34 tcpserver: warning: dropping connection, unable to read tcp.cdb: file does not exist
@4000000045e6c0812ac1fdd4 tcpserver: end 3513 status 28416
@4000000045e6c0812ac20d74 tcpserver: status: 0/40
@4000000045e6c082116237dc tcpserver: status: 1/40

[root@mail qmail]# ls /etc/tcp.
tcp.pop3      tcp.pop3.cdb  tcp.smtp      tcp.smtp.cdb

Where can the tcp.cdb be?  Thank you very much.

Best Regards,

sato






On 3/1/07, Sameer N Ingole <strike@proscrutiny.com> wrote:
Dear Sato,
Sameer N Ingole wrote:
> sato x wrote:
>> Hi Sameer. Thank you for your reply. Latest information, I've just
>> reinstalled qmail-ldap  according to the tutorial from
>> http://www.qmail-ldap.org/wiki/Full_Installation_Guide_-_Basic_Qmail_Installation,
>> yet I didn't include HDIRMAKE=-DAUTOHOMEDIRMAKE. Because you said
>> that I will need it, then I stoped qmail, commented HDIRMAKE out
>
> No. You should not comment HDIRMAKE=-DAUTOHOMEDIRMAKE because you need
> it.
> Please re read what I said. You need to uncomment it an recompile
> after stopping all qmail-ldap daemons.
> After recompile, start all qmail-ldap daemons except qmail-smtpd.
>
> Then follow this
>
> quoting from this location
> http://www.proscrutiny.com/howtos/errata-qmail-ldap.html#004
>
> ==== start quote ====
>
> Something is wrong with qmail-smtpd. Cannot receive/send mail.
>
> If for some reason you cannot get any mail through, you need to first
> zero in on the problem that is prohibiting you from sending/receiving
> mail. For this it is you would first look at the logs of qmail-smtpd
> which normally are on location /var/qmail/log/qmail-smtpd/current. If
> you find that the information in logs is not enough to debug the
> problem you would want to run qmail-smtpd with increased loglevel to
> have more verbose messages in logs. For this you will have to increase
> the LOGLEVEL which can be set in environment (tcpserver?) for
> qmail-smtpd. To do this in terminal you will have to stop qmail-smtpd.
> If you are running it using svc, you would issue following command.
>
> # svc -d /service/qmail-smtpd
>
> Above we assume that you have /var/qmail/boot/qmail-smtpd/run
> symlinked in /service with name qmail-smtpd and that it was started
>
> Then you would start qmail-smtpd with increased LOGLEVEL in a terminal
> (in screen maybe). You can do it as follows.
>
> # cd /var/qmail/boot/qmail-smtpd
> # env LOGLEVEL=255 ./run
>
> Then you would try to connect using telnet on port 25 as shown below.
>
> $ telnet yourdomain.tld 25
> Trying 10.11.111.22...
> Connected to yourdomain.tld (10.11.111.22).
> Escape character is '^]'.
> 220 yourdomain.tld ESMTP
> ehlo
> 250-yourdomain.tld
> 250-PIPELINING
> 250-DATAZ
> 250-STARTTLS
> 250-AUTH LOGIN PLAIN
> 250 8BITMIME

Here you continue with authentication etc.

>
> During this connection you would see all the messages scrolling up in
> terminal/screen where you runnning qmail-smtpd/run. You can see there
> what exactly is wrong with your setup.
>
> ==== end quote ====

--
Best Regards,

Sameer N. Ingole
http://weblogic.noroot.org/gallery2/
--
Better to light one candle than to curse the darkness.


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