Probably a special case here, but everytime the L4 probes the port, a line as added to the log. This gets a bit noisy. If a random IP connects, I'd want to see it, but maybe it would be nice to have the option to silence the log entry from certain hosts.
For now I patch it locally, but without any .conf finesse.
For example:
Nov 8 10:55:24 corppop01 dovecot: [ID 107833 mail.info] pop3-login: Disconnected: rip=172.16.253.5, lip=172.16.253.128, TLS handshake
Nov 8 10:58:00 corppop01 dovecot: [ID 107833 mail.info] pop3-login: Aborted login: rip=172.16.253.5, lip=172.16.253.128
-- Jorgen Lundman | <lundman@lundman.net> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home)
On Wed, 2006-11-08 at 11:01 +0900, Jorgen Lundman wrote:
Probably a special case here, but everytime the L4 probes the port, a line as added to the log. This gets a bit noisy. If a random IP connects, I'd want to see it, but maybe it would be nice to have the option to silence the log entry from certain hosts.
Pretty bloaty setting since pretty much no-one needs it I think.. After v1.0 I'll move to a rewritten master/config/log handling. Maybe I could then find a cleaner solution for this. If nothing else, you could replace the default log process with a script which does this :)
participants (2)
-
Jorgen Lundman
-
Timo Sirainen