Where Does Exim Store Config, Spool, and Logs?
Where the Exim mail server keeps its runtime config files, spool directories, and logs on Linux systems.
Last updated
Exim centers on one runtime config file whose name compiles into the binary, differing by distro. Spool holds queued messages with -D bodies and -H envelopes plus per-message logs. Log paths configure separately and rotate through exicyclog or system tools.
The binary knows its own paths: query flags print spool, config, and log locations authoritatively. Debian families add their own config management layer on top. Back up config plus spool plus logs together for restorable mail state. Test restores on staging first.
Where Exim stores this, by platform
/etc/exim4/exim4.conf
Single runtime config compiled into the binary; Debian variants split further. Spool holds -D and -H queue pairs with msglog branches. Logs configure separately with rotation tooling. Query the binary for authoritative paths.
Frequently asked questions
how do I back up Exim
Back up the runtime config file plus spool and log trees with the daemon paused. Compiled-in paths vary by distro, so confirm with the binary flags. Queue contents travel in the spool; logs rotate separately.
how do I move the spool or logs
Set spool_directory and log_file_path in config or at build time to relocate either tree. Per-message logs branch under msglog inside the spool. Syslog duplication settings split output further.
which config file is active
Check the compiled CONFIGURE_FILE path since names differ across distros. Debian splits update-exim4 variants while others use one file. The -bP flag prints resolved settings from the binary itself.
Notice an outdated path? Let us know.