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?
Thanks,
Ralf Corterier
________________________________________________________________
TopMail - Jetzt kostenlos anmelden - http://www.topmail.de
Auktionen.de macht Sie fit f�r den Winter! Alles f�r Body, Sport
und Wellness - damit wird die kalte Jahreszeit so heiss wie nie
zuvor! Und so g�nstig, dass Sie nicht am Heiz�l sparen m�ssen.
------------------ http://www.auktionen.de ----------------------
