hey Harm,

Here's the run file for the log -

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s2500000 n 10 /var/log/qmail/smtpd

and yeah- i figured that i'm pushing to stdout... which i expect the log/run should catch via the multilog. therefore i'm a bit confused as to how it's still getting into the smtp conversation. :)


On 9 Jun 2009, at 23:15, Harm van Tilborg wrote:

Hi James,

You are copying stderr (file descriptor 2) to your stdout (that's what the terminating 2>&1 is for). However, this log is only saved if multilog is indeed catching it.

Find in the directory where this `run' file was located the directory `log', and publish the content of the `run' file in that directory...

James Cox wrote:
On 9 Jun 2009, at 18:16, Matt Brookings wrote:
Hash: SHA1

James Cox wrote:
Anyone got any tips for how to skip those log lines? I've been looking
at the chkuser_settings and i'm not confident i've seen anything
immediately obvious. I'm also not convinced that these lines should ever
exist in the smtp conversation anyhow...

You are supposed to redirect stdout and stderr to another location. Either to /dev/null or
to logfiles.
Hmm - makes sense. This is how i'm running it, and not sure why i'm getting logs in the smtp conversation:
/usr/local/bin/tcpserver -vHR -p -x /etc/tcp.smtp.cdb \
   -u $QMAILDUID -g $NOFILESGID 0 smtp \
   /usr/local/bin/rblsmtpd \
       -r sbl-xbl.spamhaus.org \
/var/qmail/bin/qmail-smtpd /var/qmail/vpopmail/bin/vchkpw /bin/ true 2>&1
since it's running under supervise, and is logged...


Reply via email to