At 9:51 AM +0100 11/29/00, Ralf Corterier wrote:
> Hello,
>
> we are using qpopper for distributing mail within our lan. It works
> great, but there is one annoying detail I'd like to get rid off.
> Version is 3.1.2. Qpopper was compiled with configure
> --with-log-facility=LOG_LOCAL2, which will go into /var/log/qpopper.
> log. This works fine for statistics logging (qpopper is called with
> -s by inetd), but for every connect there is also an entry in
> /var/log/messages (format: popper: connect from X.X.X.X (X.X.X.X),
> where X.X.X.X is the local ip of the machine connecting).
> These entries do not show up in /var/log/popper.log, so there are
> not logged to local2. /var/log/messages is configured with
> local2.none. As statistics logging is done only to qpopper.log,
> this seems to work ok. As far as I understand the entries in /var/
> log/messages may be used for the smtp after pop feature, that some
> isp use. But since we only use qpopper internally, the entries in
> /var/log/messages are very annoying (/var/log/messages mainly
> consists of these entries). Is there any way to turn this of
> f?
What is the exact text of the message? I do not see anywhere in
Qpopper that logs "connect from" (or "Connect from"). Maybe inetd is
doing the logging?
If you compile Qpopper with debugging (use '--enable-debugging' with
./configure) then all log entries generated by Qpopper show the file
name and line number where generated.
