[Dovecot] Delivery failure about update to 1.2.4 (Debian)
Version: 1.2.4
Config: # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian squeeze/sid ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/gd_intermediate_bundle2.crt ssl_cert_file: /etc/ssl/certs/theta.crt ssl_key_file: /etc/ssl/private/theta.key ssl_key_password: obfuscated disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_location: maildir:/home/vmail/%d/%n mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 lda: log_path: /home/vmail/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: obfuscated mail_plugins: cmusieve global_script_path: /home/vmail/globalsieverc auth default: mechanisms: plain login digest-md5 user: vmail debug: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail
I recently updated Debian (testing). Now, no mail is getting from postfix to dovecot, but postfix didn't get upgraded. dovecot seems happy (after I fixed the "ssl = yes" change (speaking of which, that line is not in the dovecot -n output)), but postfix is unable to deliver email to it. Here is a sample mail.log entry:
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
I cannot seem to figure out what changed and why things are now broken. Can anyone help? Thanks.
yours,
William
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log .. Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
On Mon, 2009-10-05 at 14:59 -0400, Timo Sirainen wrote:
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log ..
lda: log_path: /home/vmail/dovecot-deliver.log ..
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
Oh, /home/vmail/dovecot-deliver.log of course. :)
On Mon, 05 Oct 2009 15:00:58 -0400 Timo Sirainen <tss@iki.fi> wrote:
On Mon, 2009-10-05 at 14:59 -0400, Timo Sirainen wrote:
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log
lda: log_path: /home/vmail/dovecot-deliver.log
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
Oh, /home/vmail/dovecot-deliver.log of course. :)
I just had a problem similar to this. I turned on all the debug (logging) in dovecot and discovered that I had to the default 0600 permissions on auth-client and auth-master, as shown below. After restarting dovecot, all went well.
srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-client= srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-master=
This is on a FreeBSD-7.2 system.
-- Jerry gesbbb@yahoo.com
Pedaeration, n.: The perfect body heat achieved by having one leg under the sheet and one hanging off the edge of the bed.
Rich Hall, "Sniglets"On Mon, Oct 05, 2009 at 03:28:24PM -0400, Jerry wrote:
On Mon, 05 Oct 2009 15:00:58 -0400 Timo Sirainen <tss@iki.fi> wrote:
On Mon, 2009-10-05 at 14:59 -0400, Timo Sirainen wrote:
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log
lda: log_path: /home/vmail/dovecot-deliver.log
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
Oh, /home/vmail/dovecot-deliver.log of course. :)
I just had a problem similar to this. I turned on all the debug (logging) in dovecot and discovered that I had to the default 0600 permissions on auth-client and auth-master, as shown below. After restarting dovecot, all went well.
srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-client= srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-master=
I am confused. The permissions above look like 0666 to me. Do I make my file look like what is above, or set it to 0600?
yours,
William nerd.cx
On Mon, 2009-10-05 at 16:43 -0400, William Witteman wrote:
On Mon, 2009-10-05 at 14:59 -0400, Timo Sirainen wrote:
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log
lda: log_path: /home/vmail/dovecot-deliver.log
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
Oh, /home/vmail/dovecot-deliver.log of course. :)
I just had a problem similar to this. I turned on all the debug (logging) in dovecot and discovered that I had to the default 0600 permissions on auth-client and auth-master, as shown below. After restarting dovecot, all went well.
srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-client= srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-master=
I am confused. The permissions above look like 0666 to me.
They are.
Do I make my file look like what is above, or set it to 0600?
If auth* permissions are wrong, an error is logged about them. So the most important thing you should do first is check if there's anything logged in dovecot-deliver.log, and if not change its permission to 0666 and see if then something gets logged there.
On Mon, 5 Oct 2009 16:43:00 -0400 William Witteman <yam@nerd.cx> wrote:
On Mon, Oct 05, 2009 at 03:28:24PM -0400, Jerry wrote:
On Mon, 05 Oct 2009 15:00:58 -0400 Timo Sirainen <tss@iki.fi> wrote:
On Mon, 2009-10-05 at 14:59 -0400, Timo Sirainen wrote:
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log
lda: log_path: /home/vmail/dovecot-deliver.log
Oct 5 14:47:07 theta postfix/pipe[30972]: 451873B5B8: to=<obfuscated>, relay=dovecot, delay=168521, delays=168521/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure)
What does deliver log to dovecot.log? If nothing, does it have enough permissions to write to it?
Oh, /home/vmail/dovecot-deliver.log of course. :)
I just had a problem similar to this. I turned on all the debug (logging) in dovecot and discovered that I had to the default 0600 permissions on auth-client and auth-master, as shown below. After restarting dovecot, all went well.
srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-client= srw-rw-rw- 1 root wheel 0B Oct 4 15:43 auth-master=
I am confused. The permissions above look like 0666 to me. Do I make my file look like what is above, or set it to 0600?
Sorry about the confusion. I had to change the settings to 0666 in order to make it work. It might work with just 0660; however, I did not have time to test it. The default 0600 definitely does not work on a FreeBSD-7.2 system (at least not mine).
-- Jerry gesbbb@yahoo.com
Q: What's the difference between a dead dog in the road and a dead lawyer in the road?
A: There are skid marks in front of the dog.
On Mon, 2009-10-05 at 14:53 -0400, William Witteman wrote:
log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log .. lda: log_path: /home/vmail/dovecot-deliver.log
If nothing is logged there, try also:
protocol lda { .. info_log_path = /home/vmail/dovecot-deliver.log }
Looks like failure to open info log file isn't logged to log_path. I'll go and fix that.
On Mon, Oct 05, 2009 at 02:53:55PM -0400, William Witteman wrote:
Version: 1.2.4
Config: # 1.2.4: /etc/dovecot/dovecot.conf
I have found the problem. I was not looking in the dovecot-deliver.log, and so I was not alerted to the cause of the error. By the way, I love the links to the wiki in the error messages - when I first upgraded and the server didn't come up automatically, it was trivial with the wiki's guidance to change to "ssl=yes".
lda: log_path: /home/vmail/dovecot-deliver.log
Here is my problem line - I noted in the changelog that this was being phased out, but I wasn't seeing the error (because it was in the deliver log) that showed me that it was this that was the problem.
mail_plugins: cmusieve
A quick comment and I was good to go. Thanks to all.
yours,
William Witteman
participants (3)
-
Jerry
-
Timo Sirainen
-
William Witteman