Adjusting logging with the "remote" syntax
Jason Young
jason at singlebit.tech
Fri Aug 21 17:17:59 EEST 2020
I wanted to follow up on this message. Is there any way to disable info logging for when the ‘remote’ is localhost?
> On Aug 12, 2020, at 12:48 PM, Jason Young <jason at singlebit.tech> wrote:
>
> According to the docs, we can use ‘local’ and ‘remote’ blocks to change configuration directives.
>
> In my current setup (Mail-in-a-box using Nextcloud, which is configured for IMAP authentication), my mail logs are spammed with local logins. I really don't need these reports, but still want to retain login logs for remote IPs. So I set the following in my configuration:
>
> remote 127.0.0.1 {
> info_log_path = /dev/null
> }
>
> When I run "doveadm -n -f remote=127.0.0.1”, it does seem to understand it:
>
> ---
> # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.21 (92477967)
> ...
> info_log_path = /dev/null
> ...
> remote 127.0.0.1 {
> info_log_path = /dev/null
> }
> ---
>
> However, I’m still getting spammed with local login reports:
>
> Aug 12 12:17:13 imap-login: Info: Login: user=<user at domain.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=29798, TLS, session=<FGVJhbCsstt/AAAB>
> Aug 12 12:17:13 imap(user at domain.tld): Info: Logged out in=305 out=2277
>
> I've also tried logging to a specific file, instead of /dev/null, but no file was created. So there must be an issue with my understanding.
>
> How can I prevent logins from localhost from being logged without sacrificing logs for all logins?
>
> -Jason Young
More information about the dovecot
mailing list