Yea but the original post wanted to record cmd's, kinda like tcpservers -v
option. Sure you can sniff and dump etc, but nothing built in (aka fool
proof).
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Wed, 17 Nov 1999, eric wrote:
>
> Why don't you just sniff the port grabbing inbound packets only?
>
> Maybe use tcpdump with tcpslice.
>
> On Wed, 17 Nov 1999 [EMAIL PROTECTED] wrote:
>
> ; I have
> ;
> ; mail.* /var/log/maillog
> ;
> ; and get no pop3 commands. I do get splogger messages, but the original
> ; post wanted the cmds passed to/from the POP daemon.
> ;
> ; My syslog line above should dump all facility type mail of any level to
> ; the maillog.
> ;
> ; To "see" and record the commands passed to pop3d from the client (user,
> ; pass, list, etc) wouldn't you need to tap into the session or tell
> ; qmail-pop3d via an internal function (sprintf, syslog) to output those
> ; commands?
> ;
> ; Paul Farber
> ; Farber Technology
> ; [EMAIL PROTECTED]
> ; Ph 570-628-5303
> ; Fax 570-628-5545
> ;
> ; On Wed, 17 Nov 1999, eric wrote:
> ;
> ; > On Wed, 17 Nov 1999 [EMAIL PROTECTED] wrote:
> ; >
> ; > ; Tcpserver only handles the connection part of the process.
> ; > ;
> ; > ; neither man page for qmail-pop3d or qmail-popup listed any
> ; > ; debugging/logging options.
> ; >
> ; > That is because they log to syslog.
> ; >
> ; > # grep mail.debug /etc/syslog.conf
> ; > mail.debug /var/log/mail.log
> ; >
> ; > check there.
> ; >
> ; >
> ;
> ;
>
> --
> Eric Pancer @ "I don't give advice; geniuses don't
> [EMAIL PROTECTED] ! need it, and amateurs don't want it."
> http://www.catastrophe.net | -- Vida Chenoweth
>
>
