search for: mlagob147jd

...uth > attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, > session=<bWd0nr14SuF/AAAB> > Oct 21 15:05:29 osaka dovecot[1256]: imap-login: Aborted login (no auth > attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, > session=<MlAGob147Jd/AAAB> How can I disable logging these actions from 127.0.0.1? Thanks, Andr? -- https://github.com/progmaticltd/homebox

...ts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, >> secured, session=<bWd0nr14SuF/AAAB> >> Oct 21 15:05:29 osaka dovecot[1256]: imap-login: Aborted login (no >> auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, >> secured, session=<MlAGob147Jd/AAAB> > > How can I disable logging these actions from 127.0.0.1? Presumably you are concerned not so much with having these lines in the logfile, as you are with your monitoring software seeing them and generating alarms because they are reported to syslog as errors.? If I'm wron...

...ser=<>, rip=127.0.0.1, lip=127.0.0.1, >>> secured, session=<bWd0nr14SuF/AAAB> >>> Oct 21 15:05:29 osaka dovecot[1256]: imap-login: Aborted login (no >>> auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, >>> secured, session=<MlAGob147Jd/AAAB> >> >> How can I disable logging these actions from 127.0.0.1? > > Presumably you are concerned not so much with having these lines in > the logfile, as you are with your monitoring software seeing them and > generating alarms because they are reported to syslog as...