On Saturday 12 January 2008 09:54:03 Timo Sirainen wrote:
> On Thu, 2008-01-10 at 18:53 +0100, Daniel wrote:
> > > > deliver(leva): Can't connect to auth server
> > > > at /var/run/dovecot/auth-master: Connection refused
> > > > postfix/pipe[8582]: 8A1C6F261: to=<[EMAIL PROTECTED]>,
> > > > orig_to=<id>, relay=dovecot-lda, delay=1.7, delays=1.1/0/0/0
> > > > .68, dsn=2.0.0, status=sent (delivered via dovecot-lda service)
> > > > postfix/qmgr[29441]: 8A1C6F261: removed
>
> I don't know why this would happen though. How are you executing
> deliver? I think the problem is with Postfix configuration or at
> least outside deliver.
Currently, I'm executing deliver from a wrapper script:
# master.cf:
dovecot-lda unix [...] argv=[...]/dovecot-lda_wrapper.pl ${recipient}
That script finds out the username which must be passed to deliver's -d
option, because dovecot's user names are not the same as the recipient
email addresses of the user's, so I can not just execute deliver
directly with the -d ${recipient} option. This hack prevented deliver's
exit code to get recognized by postfix.
>
> > Maybe my auth-master file remains there, but deliver couldn't
> > connect to it, because dovecot has died. I guess the socket stayed
> > there because dovecot couldn't clean up after itself in this case.
> > Am I wrong (just guessing leastways...)?
>
> I tested that in that situation deliver also returns temporary
> failure.
Daniel
