On Thu, 2009-01-08 at 17:02 -0500, Thomas Harold wrote: > >> My first inclination was to look at the dovecot-deliver.log file (per > >> log_path or info_log_path). It wasn't until I went looking for SELinux > >> errors that I discovered that it was a labeling problem. > > > > That's what I meant, did Dovecot not log anything? > > > > None that I could find. At 14:48, there's nothing in the > dovecot-deliver.log file (set in the "protocol lda" section of our > dovecot.conf).
Well, that logs only deliver's errors. > But our logging section at the top of the dovecot.conf file is: > > ## > ## Logging > ## > > # Log file to use for error messages, instead of sending them to syslog. > # /dev/stderr can be used to log into stderr. > #log_path = /var/log/dovecot.log > > # Log file to use for informational and debug messages. > # Default is the same as log_path. > #info_log_path = > > So I'm not sure that is configured correctly to actually log errors. They get logged to syslog, which probably goes to mail.log or something like that.
signature.asc
Description: This is a digitally signed message part
