Michael Bowe wrote:

At 01:29 AM 9/19/2003, X-Istence wrote:

So then we started getting these messages in our logs:

@400000003f69830f2c2df1b4 info msg 47: bytes 1153 from
<*************> qp 70866 uid 0
@400000003f69830f2ca1d1c4 starting delivery 60: msg 47 to local
@400000003f69830f2cae02dc status: local 1/10 remote 0/20
@400000003f69830f34a902ac delivery 60: success: did_0+0+1/
@400000003f69830f34c072ac status: local 0/10 remote 0/20
@400000003f69830f34c0a18c end msg 47

This was basically allready better than having it fail to call
vdelivermail, but this is still wrong, as an entry should look like

@400000003f69850e2b908cbc info msg 94300: bytes 5286 from
<******************> qp 41793 uid 0
@400000003f69850e2bb94684 starting delivery 4877: msg 94300 to local
@400000003f69850e2bbf0efc status: local 1/10 remote 0/20
@400000003f69850e2c7fcebc delivery 4877: success:


@400000003f69850e2c91c07c status: local 0/10 remote 0/20
@400000003f69850e2c91d7ec end msg 94300

The messages are NOT being delivered. That is what i meant to prove by
the differences in the log files, sorry if i didnt make this clear.

The logs on my working 5.3.27 server look like your first example, not the second.

Can't say I recall ever seeing anyone post logs that look like your second

Are you sure you didn't apply some sort of patch to your other qmail server
to achieve that more "detailed" logging?


Nope, this is my run script on both servers for smtpd:

exec 2>&1 \
envdir ./env \
sh -c '
   case "$REMOTENAME" in h) H=;; p) H=p;; *) H=H;; esac
   case "$REMOTEINFO" in r) R=;; [0-9]*) R="t$REMOTEINFO";; *) R=R;; esac
   exec \
   envuidgid root \
   softlimit ${DATALIMIT+"-d$DATALIMIT"} \
   /usr/local/bin/tcpserver \
       -vDU"$H$R" \
       ${LOCALNAME+"-l$LOCALNAME"} \
       ${BACKLOG+"-b$BACKLOG"} \
       -xtcp.cdb \
       -- "${IP-0}" "${PORT-25}" \
   /var/qmail/bin/qmail-smtpd /usr/local/vpopmail/bin/vchkpw /usr/bin/true


exec \
setuidgid qmaill \
envdir ./env \
sh -c '
   exec \
   multilog \
       t \

I wouldnt know where the extra stuff comes from. Just did a reinstall of everything, just to check once again, and now its working, as long as i chmod those directories correctly. Ill have to talk to the maintainer of the FreeBSD vpopmail port to get it fixed.

Thanks to the list, i got it working. :)

Reply via email to