DOVEADM-LOG(1)
β¨ DOVEADM-LOG β¨
okay bestie, welcome to doveadm-log β the part of the Dovecot manual that's all about your log files. this is the doveadm-log(1) page, and honestly? it's giving "find, test, or reopen" energy. that's literally the whole vibe. π
π¦ NAME π¦
doveadm-log β locate, test or reopen Dovecot's log files
ngl the name kinda says it all, but let's go anyway because there are details and details are the moment.
πΈ SYNOPSIS πΈ
doveadm [GLOBAL OPTIONS] log errors [-s min_timestamp]
doveadm [GLOBAL OPTIONS] log find [directory]
doveadm [GLOBAL OPTIONS] log reopen
doveadm [GLOBAL OPTIONS] log test
four little incantations. pick your fighter. π
π DESCRIPTION π
so the doveadm log commands exist to locate and reopen the log files of dovecot(1). that's the job. that's what they do.
and because that wasn't enough main character energy, you can also test the configured targets of the log_path settings. so if you've ever been like "is this even going anywhere??" β yes, there's a command for that. slay. β¨
π GLOBAL OPTIONS π
these are the global doveadm(1) options, shared across the whole doveadm situation:
-Dβ turns on verbosity and debug messages. more noise, more truth.-Oβ do not read any config file, just use defaults. important bit: thedovecot_storage_versionsetting defaults to the latest version here, but you can override it with-o.-kβ preserve the entire environment fordoveadm, not just theimport_environmentsetting.-vβ enables verbosity, including a progress counter</>progress counter. (the little numbers going up? iconic.)-iinstance-name β if you're running multiple Dovecot instances, pick which config file to use based on this instance name. see theinstance_namesetting for more on that.-cconfig-file β read configuration from the given config-file. by default it first reads the config socket, and then falls back to/etc/dovecot/dovecot.conf. you can also point this at the config socket of some instance running a compatible version. flexible fr fr.-osetting=value β overrides the configuration setting from/etc/dovecot/dovecot.confand from the userdb with the given value. want to override multiple settings? just pass-omultiple times, one per setting. no cap.
π« COMMANDS π«
π log errors
doveadm [GLOBAL OPTIONS] log errors [-s min_timestamp]
the log errors command shows you the last errors and warnings β up to 1,000 of them. and here's the cute part: if no output is generated, that means no errors have occurred since the last start. silence = good news, bestie. π«Ά
-smin_timestamp β an integer value representing seconds since the epoch, aka a Unix timestamp. when you give a min_timestamp,doveadm(1)will only show errors that occurred since that point in time. time travel but make it logs.
π§ log find
doveadm [GLOBAL OPTIONS] log find [directory]
the log find command shows you the location of the log files, the ones dovecot(1) logs its messages to through syslogd(8). and if doveadm(1) couldn't find any log files on its own, no stress β you can specify the directory where your syslogd writes its log files. teamwork. π
π log reopen
doveadm [GLOBAL OPTIONS] log reopen
this one makes doveadm send a SIGUSR1 signal to the master process, which causes it to reopen all log files configured in the log_path, info_log_path and debug_log_path settings. those settings live in /etc/dovecot/conf.d/10-logging.conf.
the master process also signals the log process to do the same thing. this is mainly useful after manually rotating the log files β you know, the classic logrotate moment. π₯
β log test
doveadm [GLOBAL OPTIONS] log test
this one makes doveadm write the message "This is Dovecot's priority log (timestamp)" to the configured log files. the priorities it uses are: debug, info, warning, error and fatal. so you get one of each. a little sampler platter of log levels. adorable. π
πΈ EXAMPLE πΈ
here's how you locate the log files used by dovecot(1):
doveadm log find
Looking for log files from /var/log
Debug: /var/log/dovecot.debug
Info: /var/log/mail.log
Warning: /var/log/mail.log
Error: /var/log/mail.log
Fatal: /var/log/mail.log
see how everything funnels into /var/log/mail.log except debug? yeah. that's the vibe check. π
π REPORTING BUGS π
found a bug? (not me manifesting it, but like, hypothetically.) report it β including your doveconf -n output β to the Dovecot Mailing List at β¨dovecot@dovecot.orgβ©.
info about reporting bugs lives at: β¨https://dovecot.org/bugreport.htmlβ©
π¦ SEE ALSO π¦
and that's the whole page, bestie!! this was doveadm-log(1) from f979264, April 2026. go forth, find your logs, rotate them, reopen them, test them. main character sysadmin behaviour, periodt. π
β¨π
π¦ where this page comes from
- alpine 3.23: dovecot-doc 2.4.5-r0 Β· MIT AND LGPL-2.1-or-later
- alpine 3.24: dovecot-doc 2.4.5-r0 Β· MIT AND LGPL-2.1-or-later
- arch rolling: dovecot 2.4.5-1 Β· MIT AND LGPL-2.1-only
- fedora 43: dovecot 1:2.4.5-1.fc43 Β· MIT AND LGPL-2.1-only
- fedora 44: dovecot 1:2.4.5-1.fc44 Β· MIT AND LGPL-2.1-only
- nixos 26.05: dovecot 2.4.5
- nixpkgs unstable: dovecot 2.4.5
- opensuse-leap 16.0: dovecot24 2.4.5-160000.1.1 Β· BSD-3-Clause AND LGPL-2.1-or-later AND MIT
- opensuse-leap 16.0: dovecot24 2.4.5-160000.1.1 Β· BSD-3-Clause AND LGPL-2.1-or-later AND MIT
- opensuse-leap 16.0: dovecot24 2.4.5-160000.1.1 Β· BSD-3-Clause AND LGPL-2.1-or-later AND MIT
- opensuse-leap 16.0: dovecot24 2.4.5-160000.1.1 Β· BSD-3-Clause AND LGPL-2.1-or-later AND MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms