Hey,
Here's an (edited) example of a smtp conversation, with a netqmail
install with smtp auth and chkuser patches:
220 mail.23i.net ESMTP
EHLO imaj.es
250-mail.23i.net
250-AUTH LOGIN CRAM-MD5 PLAIN
250-AUTH=LOGIN CRAM-MD5 PLAIN
250-PIPELINING
250 8BITMIME
AUTH LOGIN
334 VXNlcm5hbWU6
334 UGF
-BEGIN PGP SIGNED MESSAGE-
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
On 9 Jun 2009, at 18:16, Matt Brookings wrote:
-BEGIN PGP SIGNED MESSAGE-
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 t
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'
hey Harm,
Here's the run file for the log -
exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t
s250 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
Hi James,
What version of chkuser are you using?
When I look at the 2.0.9 source, I see the following lines inside
chkuser_settings.h:
/*
* the following line enables debugging of chkuser
*/
/* #define CHKUSER_DEBUG */
/*
* The following line moves DEBUG output from STDOUT (default) to ST
I've had it running for a few hours, and have this:
1 CHKUSER rejected relaying
5 CHKUSER accepted any rcpt
28 CHKUSER relaying rcpt
362 CHKUSER accepted rcpt
1719 CHKUSER rejected rcpt
1758 CHKUSER accepted sender
and... in my defines...
neither of those two are enabl
