I did some testing on a Debian testing VM. I built 2.0.17 from sources and copied the config straight over from the malfunctioning machine.

LDA logging worked. So, it could be something about my system. But, running /usr/lib/dovecot/deliver still doesn't return a value on the command line as documented on the wiki.

I've attached strace files from both the malfunctioning Debian packages machine and the built from sources VM. Unfortunately, I'm a new strace user, so I don't know what it all means.

Michael

--- On Tue, 1/3/12, Timo Sirainen <tss_no_spam@iki.fi> wrote:

From: Timo Sirainen <tss_no_spam@iki.fi> Subject: Re: [Dovecot] Newbie: LDA Isn't Logging To: "Michael" <mpapet_no_spam@yahoo.com> Cc: dovecot@dovecot.org Date: Tuesday, January 3, 2012, 4:15 AM On Mon, 2012-01-02 at 22:48 -0800, Michael wrote:

...

Hi,

I'm a newbie having some trouble getting deliver to log anything.  Related to this, there are no return values unless the -d is missing.  I'm using LDAP to store virtual domain and user account information.

Test #1: /usr/lib/dovecot/deliver -e -f mpapet@yahoo.com -d zed@mailswansong.dom < bad.mail Expected result: supposed to fail, there's no zed account via ldap lookup and supposed to get a return code per the wiki at http://wiki2.dovecot.org/LDA.  Supposed to log too. Actual result: nothing gets delivered, no return code, nothing is logged.

As in return code is 0? Something's definitely wrong there then.

First check that deliver at least reads the config file. Add something broken in there, such as: "foo=bar" at the beginning of dovecot.conf. Does deliver fail now?

Also running deliver via strace could show something useful.