On Oct 18, 2008, at 4:00 AM, Timo Sirainen wrote:
On Fri, 2008-10-17 at 12:47 -0700, Lucas Madar wrote:
I turned on delivery logging to see what I'd get, and I simply get
this: deliver(xxxxxx@xxxxx.xxx): Oct 17 00:36:22 Info: Loading modules from directory: /usr/local/lib/dovecot/lda deliver(xxxxxx@xxxxx.xxx): Oct 17 00:36:22 Info: Module loaded: /usr/ local/lib/dovecot/lda/lib90_cmusieve_plugin.so (normally, here it would print out more info about the user, as "auth input" lines, but it doesn't when it fails in this way)Applying this patch probably makes it log that "auth lookup failed": http://hg.dovecot.org/dovecot-1.1/rev/b085c58fcf14
But in that case the auth process should already have logged errors.
I applied this patch and now I get:
deliver(x@x): Oct 21 09:51:55 Info: Loading modules from directory: / usr/local/lib/dovecot/lda deliver(x@x): Oct 21 09:51:55 Info: Module loaded: /usr/local/lib/ dovecot/lda/lib90_cmusieve_plugin.so deliver(x@x): Oct 21 09:51:55 Error: Auth lookup returned failure
The auth process is not logging any errors. I suppose I can stick more
debugs into the auth process and see what happens. I'm using mysql as
an auth backend, and the server isn't particularly loaded. Any other
ideas?
log_path: /var/log/pickup.log info_log_path: /var/log/pickup.log
I'd suggest using different files for these. Errors are written to log_path, and that log file should always stay empty. It's a lot
easier to notice errors when they're not surrounded by a lot of useless logging.I guess you could already just grep for "Error:" or "Warning:" from
the pickup.log to see if there are some auth errors.
My server is relatively low traffic, which does not make these logs
too busy to read.
Thanks, Lucas