Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | RSS feed
#### Log destination.### Log file to use for error messages. "syslog" logs to syslog,# /dev/stderr logs to stderr.#log_path = syslog# Log file to use for informational messages. Defaults to log_path.#info_log_path =# Log file to use for debug messages. Defaults to info_log_path.#debug_log_path =# Syslog facility to use if you're logging to syslog. Usually if you don't# want to use "mail", you'll use local0..local7. Also other standard# facilities are supported.#syslog_facility = mail#### Logging verbosity and debugging.### Log filter is a space-separated list conditions. If any of the conditions# match, the log filter matches (i.e. they're ORed together). Parenthesis# are supported if multiple conditions need to be matched together.# Supported conditions are:# event:<name wildcard> - Match event name. '*' and '?' wildcards supported.# source:<filename>[:<line number>] - Match source code filename [and line]# field:<key>=<value wildcard> - Match field key to a value. Can be specified# multiple times to match multiple keys.# cat[egory]:<value> - Match a category. Can be specified multiple times to# match multiple categories.# For example: event:http_request_* (cat:error cat:storage)# Filter to specify what debug logging to enable. This will eventually replace# mail_debug and auth_debug settings.#log_debug =# Crash after logging a matching event. For example category:error will crash# any time an error is logged, which can be useful for debugging.#log_core_filter =# Log unsuccessful authentication attempts and the reasons why they failed.#auth_verbose = no# In case of password mismatches, log the attempted password. Valid values are# no, plain and sha1. sha1 can be useful for detecting brute force password# attempts vs. user simply trying the same password over and over again.# You can also truncate the value to n chars by appending ":n" (e.g. sha1:6).#auth_verbose_passwords = no# Even more verbose logging for debugging purposes. Shows for example SQL# queries.#auth_debug = no# In case of password mismatches, log the passwords and used scheme so the# problem can be debugged. Enabling this also enables auth_debug.#auth_debug_passwords = no# Enable mail process debugging. This can help you figure out why Dovecot# isn't finding your mails.#mail_debug = no# Show protocol level SSL errors.#verbose_ssl = no# mail_log plugin provides more event logging for mail processes.plugin {# Events to log. Also available: flag_change append#mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename# Available fields: uid, box, msgid, from, subject, size, vsize, flags# size and vsize are available only for expunge and copy events.#mail_log_fields = uid box msgid size}#### Log formatting.### Prefix for each line written to log file. % codes are in strftime(3)# format.#log_timestamp = "%b %d %H:%M:%S "# Space-separated list of elements we want to log. The elements which have# a non-empty variable value are joined together to form a comma-separated# string.#login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c# Login log format. %s contains login_log_format_elements string, %$ contains# the data we want to log.#login_log_format = %$: %s# Log prefix for mail processes. See doc/wiki/Variables.txt for list of# possible variables you can use.#mail_log_prefix = "%s(%u)<%{pid}><%{session}>: "# Format to use for logging mail deliveries:# %$ - Delivery status message (e.g. "saved to INBOX")# %m / %{msgid} - Message-ID# %s / %{subject} - Subject# %f / %{from} - From address# %p / %{size} - Physical size# %w / %{vsize} - Virtual size# %e / %{from_envelope} - MAIL FROM envelope# %{to_envelope} - RCPT TO envelope# %{delivery_time} - How many milliseconds it took to deliver the mail# %{session_time} - How long LMTP session took, not including delivery_time# %{storage_id} - Backend-specific ID for mail, e.g. Maildir filename#deliver_log_format = msgid=%m: %$