Peter..
I have recompied vpopmail and got the following configuration output. After
the vpopmail authentication, I can see the modification date of
"/etc/tcp.smtp.cdb" gets changed. So, there seeems to be no problem with the
database update. The command output of "/home/vpopmail/bin/clearopensmtp
2>&1 > /dev/null ; $?"  gives 0 (null) . And the tcp.smtp.tmp.xxx files are
no more generated, probably this was caused by the failure of opening the
wrong tcp.smtp.cdb yesterday.
Thank you for your valuable help.
Danke schon..

Chuss

Ihsan
-------------------------------------------

vpopmail directory = /home/vpopmail
               uid = 589
               gid = 589
          ip alias = OFF --enable-ip-alias-domains=n (default)
address extentions = OFF --enable-qmail-ext=n (default)
     roaming users = ON  --enable-roaming-users=y
    tcpserver file = /etc/tcp.smtp
    open_smtp file = /home/vpopmail/etc/open-smtp
        user quota = OFF --enable-defaultquota=NOQUOTA default
table optimization = many domains --enable-many-domains=y default
       auth module = cdb default
  system passwords = OFF --enable-passwd=n default
      file locking = ON  --enable-file-locking=y default
         file sync = OFF --enable-file-sync=n default disable vdelivermail
fsync
      auth logging = ON  --enable-auth-logging=y default
     mysql logging = OFF --enable-mysql-logging=n default
      clear passwd = ON  --enable-clear-passwd=y (default)
 valias processing = OFF --enable-valias=n
        pop syslog = log everything, including passwords in errors
                     --enable-logging=v
    default domain =  --enable-default-domain=
          auth inc = -Icdb
          auth lib = 


-----Original Message-----
From: Peter Palmreuther [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 7:49 PM
To: [EMAIL PROTECTED]
Subject: Re: [vchkpw] I can not "telnet 127.0.0.1 25" .Connection closed
b y foreign hos t


Hi _hsan,

"Please don't CC me ..." doesn't mean "Please don't answer on-list.".

On Mon, 3 Mar 2003 18:10:04 +0200 _hsan  Turkmen <[EMAIL PROTECTED]>
wrote:
[full quote because answering to the list to a mail not directed there]

> Thanks Peter..
> The problem was that I accidentally chaged "-x /etc/tcp.smtp.cdb" portion
of
> the script  as "-x /etc/tcp.smtp". It is fixed now by your valuable help.I
> wonder why my ~vpopmail/etc/ folder has many temporary files and "40 * * *
*
> /home/vpopmail/bin/clearopensmtp 2>&1 > /dev/null" line in crontab does
not
> clear temporary files. (Another awkward question again). I guess it was
> becouse of the above failure..right?. 
> 
> 
> 
> -rw-r--r--    1 vpopmail vchkpw         25 Mar  3 14:54 inc_deps
> -rw-r--r--    1 vpopmail vchkpw         32 Mar  3 14:54 lib_deps
> -rw-r--r--    1 vpopmail vchkpw         60 Mar  3 17:40 open-smtp
> -rw-r--r--    1 root     root            0 Mar  3 17:52 open-smtp.lock
> -rw-r--r--    1 root     root            0 Mar  3 16:19 open-smtp.tmp.1318
> -rw-r--r--    1 root     root            0 Mar  3 16:30 open-smtp.tmp.1341
> -rw-r--r--    1 root     root            0 Mar  3 16:40 open-smtp.tmp.1660
> -rw-r--r--    1 root     root            0 Mar  3 16:50 open-smtp.tmp.1662
> -rw-r--r--    1 root     root            0 Mar  3 17:00 open-smtp.tmp.1691
> -rw-r--r--    1 root     root            0 Mar  3 17:11 open-smtp.tmp.1717
> -rw-r--r--    1 root     root            0 Mar  3 17:21 open-smtp.tmp.1745
> -rw-r--r--    1 root     root            0 Mar  3 17:31 open-smtp.tmp.1747
> -rw-r--r--    1 root     root            0 Mar  3 17:42 open-smtp.tmp.1860
> -rw-r--r--    1 root     root            0 Mar  3 17:52 open-smtp.tmp.2509
> -rw-r--r--    1 vpopmail vchkpw         95 Mar  2 05:12 tcp.smtp
> 
> 
> 
> Thanks for your help..

I don't think a "run every 40 minutes" cron is the primary reason for
"every 10 minutes created" files.
But OTOH the file names look like those clearopensmtp uses.

I'd suggest you:

1.) Tell us the _complete_ configure line used for compiling vpopmail,
  for us being able to figure out what .cdb file clearopensmtp tries to
  re-create.

2.) run 'clearopensmtp' on command line and tell us potential output and
  the result of
  'clearopensmtp 2>&1 >/dev/null; echo $?'
  for us being able to see if clearopensmtp states it ran successfully.
-- 
Peter

Reply via email to