-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17 Nov 99, at 11:28, Steve Kapinos wrote:
> So there is the supervise process, followed by accustamp, and cyclog for
> both smtpd and pop3 (lines truncated).
>
> Checking permissions on dirs cyclog is pointed to..
>
> [root@hootch qmail]# ls -l | grep qmail-
> drwxrwxr-x 2 qmaill nofiles 4096 Nov 17 12:20 qmail-pop3d
> drwxrwxr-x 2 qmaill nofiles 4096 Nov 17 12:20 qmail-smtpd
They don't need to be writable by nofiles (but it doesn't matter
anyway).
> here's a sample:
>
> [root@hootch /etc]# cd /var/log/qmail
> [root@hootch qmail]# cat ./qmail-smtpd/*
> 942859225.677233 tcpserver: status: 1/40
> 942859225.678613 tcpserver: pid 16302 from 12.35.161.57
> 942859225.700022 tcpserver: ok 16302
> mail.tandbergapplications.com:12.35.161.8:25
> dhcp-57.tandbergusa.com:12.35.161.57::1288
> 942859225.720118 bash: /home/jobu/.bashrc: Permission denied
Now this is interesting. Why indeed does bash think it should use
a .bashrc in /home/jobu? You are running smtp as qmaild, aren't
you? What's qmaild's home directory?
> [root@hootch qmail]# cat ./qmail-pop3d/*
> 942859335.990191 tcpserver: status: 1/40
> 942859335.991045 tcpserver: pid 16310 from 12.35.161.57
> 942859336.013881 tcpserver: ok 16310
> mail.tandbergapplications.com:12.35.161.8:110
> dhcp-57.tandbergusa.com:12.35.161.57::1290
> 942859336.353578 tcpserver: end 16310 status 256
> 942859336.353787 tcpserver: status: 0/40
> 942859647.757874 tcpserver: status: 1/40
> 942859647.758543 tcpserver: pid 16331 from 12.35.161.57
> 942859647.779994 tcpserver: ok 16331
> mail.tandbergapplications.com:12.35.161.8:110
> dhcp-57.tandbergusa.com:12.35.161.57::1293
> 942859647.895205 tcpserver: end 16331 status 256
> 942859647.895417 tcpserver: status: 0/40
That's exactly what you should be seeing - that's what tcpserver -v
does.
> First thing I saw was that bashrc error. Looking at ~jobu, the bashrc
> file points back to the system wide /etc/bashrc, which only contains 1
> line.
Yes, but why does qmaild need to look into ~jobu?
> So back to the pop3d logging.. I would expect to see some sort of auth
> logging or something, yet it looks near identical to the smtpd logging.
> Am I just missing the boat here or what?
If you want to have more logging, you need to patch (preferably)
checkpassword to output the username and/or authentication
status to stderr (or stdout?). There was no logging intended AFAIK.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBODLpvFMwP8g7qbw/EQLZrACeP0222+nDvz65voIcwe7MdqMTXn0AoJyO
UjpEDPZfP42QLtJlvC8T+ODz
=j9fg
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
