[Dovecot] Dovecot LDA failure in RC16
After upgrading a test server from rc15 to rc16, Postfix was no longer able to deliver mail via Dovecot deliver:
Jan 5 11:00:59 testhost postfix/local[8873]: 497282EFE: to=<testuser@testhost>, relay=local, delay=1.2, delays=0.13/0.02/0/1, dsn=5.3.0, status=bounced (Command died with status 89: "/opt/dovecot/libexec/dovecot/deliver -f "$SENDER"")
Should "status 89" mean something to me? How can I debug this?
--
Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs@umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593
On 5.1.2007, at 19.12, Steven F Siirila wrote:
After upgrading a test server from rc15 to rc16, Postfix was no
longer able to deliver mail via Dovecot deliver:Jan 5 11:00:59 testhost postfix/local[8873]: 497282EFE:
to=<testuser@testhost>, relay=local, delay=1.2,
delays=0.13/0.02/0/1, dsn=5.3.0, status=bounced (Command died with
status 89: "/opt/dovecot/libexec/dovecot/deliver -f "$SENDER"")Should "status 89" mean something to me? How can I debug this?
It should log the actual error message into Dovecot's log file. If
not, you haven't given enough permissions to write to the logs
(http://wiki.dovecot.org/LDA -> Logging).
On Fri, Jan 05, 2007 at 08:26:41PM +0200, Timo Sirainen wrote:
On 5.1.2007, at 19.12, Steven F Siirila wrote:
After upgrading a test server from rc15 to rc16, Postfix was no
longer able to deliver mail via Dovecot deliver:Jan 5 11:00:59 testhost postfix/local[8873]: 497282EFE:
to=<testuser@testhost>, relay=local, delay=1.2,
delays=0.13/0.02/0/1, dsn=5.3.0, status=bounced (Command died with
status 89: "/opt/dovecot/libexec/dovecot/deliver -f "$SENDER"")Should "status 89" mean something to me? How can I debug this?
It should log the actual error message into Dovecot's log file. If
not, you haven't given enough permissions to write to the logs
(http://wiki.dovecot.org/LDA -> Logging).
Is there a reason that deliver doesn't log through the master process?
In any event, I set up a world-writable LDA log file and it revealed:
deliver(myuser): Info: Loading modules from directory: /opt/dovecot/lib/dovecot/lda deliver(myuser): Fatal: Multiple files for module convert_plugin: /opt/dovecot/lib/dovecot/lda/lib20_convert_plugin.so, /opt/dovecot/lib/dovecot/lda/lib01_convert_plugin.so
It seems that the file name of some plugins has changed:
lib01_convert_plugin -> lib20_convert_plugin
lib01_quota_plugin -> lib10_quota_plugin
lib02_trash_plugin -> lib11_trash_pluginSo, it seems that part of an upgrade to RC16 should involve removing the entire Dovecot '/lib/' hierarchy (or at least removing the old files after installation). Or is there something else I'm missing here?
--
Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs@umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593
On 5.1.2007, at 21.09, Steven F Siirila wrote:
So, it seems that part of an upgrade to RC16 should involve removing the entire Dovecot '/lib/' hierarchy (or at least removing the old files after installation).
Yes, like the release announcement said.
* Priority numbers in plugin names have changed. If you're installing
from source, you should delete the existing plugin files before
installing the new ones, otherwise you'll get errors.On 5.1.2007, at 21.09, Steven F Siirila wrote:
It should log the actual error message into Dovecot's log file. If not, you haven't given enough permissions to write to the logs (http://wiki.dovecot.org/LDA -> Logging).
Is there a reason that deliver doesn't log through the master process?
Oh, and as for this. Normally all Dovecot processes are started via
the master process, but deliver is started independently. Maybe in
future I'll make deliver binary be some kind of a simple proxy and
have the actual delivery done by a process started by master process
(maybe write a LMTP server and have deliver be a LMTP client?).
participants (2)
-
Steven F Siirila
-
Timo Sirainen