[Dovecot] configuring lda
after coping lda stanza into the config file, I get "unknown protocol name" error. adding lda to the list of protocols doesn't seem to do the trick.
lda was built during compile and the binary is present, piping into it manually spits error messages about missing config, so how do I go about the problem above ?
It is my undertanding that using dovecot-lda would help maintain the indexes in proper state ( as opposed to using procmail and having to rebuild indexes from scratch upon delivery of large amounts of mail ) ?
mucho gracias to you all.
protocol lda { # If you wish to use plugins you need to specify plugin directory # For example quota enforcing is implemented by plugin #module_dir = /usr/local/lib/dovecot/lda
# Address from LDA should send MDNs like out of quota postmaster_address = postmaster@your.dom
# If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path =
# UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot-auth-master }
On Thu, 2006-02-02 at 13:35 -0500, Lenny wrote:
after coping lda stanza into the config file, I get "unknown protocol name" error. adding lda to the list of protocols doesn't seem to do the trick.
This looks like you're running too old Dovecot version. Versions before 1.0.beta1 didn't like having "protocol lda" in dovecot.conf.
It is my undertanding that using dovecot-lda would help maintain the indexes in proper state ( as opposed to using procmail and having to rebuild indexes from scratch upon delivery of large amounts of mail ) ?
Well, not completely rebuild. It only adds the newly found mails.
On Thu, 2006-02-02 at 13:35 -0500, Lenny wrote:
after coping lda stanza into the config file, I get "unknown protocol name" error. adding lda to the list of protocols doesn't seem to do the trick.
This looks like you're running too old Dovecot version. Versions before 1.0.beta1 didn't like having "protocol lda" in dovecot.conf.
No, I'm running the very latest version. v1.0 beta2. Compiled with default options, just added LDFLAGS for ssl libs. Like I said /usr/local/dovecot/libexec/dovecot/deliver is present.
It is my undertanding that using dovecot-lda would help maintain the indexes in proper state ( as opposed to using procmail and having to rebuild indexes from scratch upon delivery of large amounts of mail ) ?
Well, not completely rebuild. It only adds the newly found mails.
With large mbox folders, 10000+ messages with delivery 10-15 messages per minute, I wasn't even able to connect to the folder at all. I would only get time out errors. Meanwhile, wu-imap worked fine with same folder, although not very fast. I assumed it was either a problem with locking ( fcntl - solaris) or index rebuilds.
Thank you for the reply.
On Sat, 2006-02-04 at 09:35 -0500, Lenny wrote:
On Thu, 2006-02-02 at 13:35 -0500, Lenny wrote:
after coping lda stanza into the config file, I get "unknown protocol name" error. adding lda to the list of protocols doesn't seem to do the trick.
This looks like you're running too old Dovecot version. Versions before 1.0.beta1 didn't like having "protocol lda" in dovecot.conf.
No, I'm running the very latest version. v1.0 beta2. Compiled with default options, just added LDFLAGS for ssl libs. Like I said /usr/local/dovecot/libexec/dovecot/deliver is present.
Well, that error message comes if Dovecot's master binary doesn't recognize the name in "protocol name {". If it's not "imap", "pop3" or "lda" this error comes. So if you had "protocol lda {" in there without any typos or some other weirdness, the only possibility is that the error message didn't come from beta2..
It is my undertanding that using dovecot-lda would help maintain the indexes in proper state ( as opposed to using procmail and having to rebuild indexes from scratch upon delivery of large amounts of mail ) ?
Well, not completely rebuild. It only adds the newly found mails.
With large mbox folders, 10000+ messages with delivery 10-15 messages per minute, I wasn't even able to connect to the folder at all. I would only get time out errors. Meanwhile, wu-imap worked fine with same folder, although not very fast. I assumed it was either a problem with locking ( fcntl - solaris) or index rebuilds.
Did Dovecot print any errors to its log files then? And this was with 1.0beta?
I don't really see why Dovecot would work here differently than UW-IMAP. Indexes shouldn't be the problem.. With 0.99.x I could undestand that it keeps resyncing the whole mbox every time a new mail comes, but 1.0beta should just be looking at the new mails once it has done the initial sync (unless you changed mbox_dirty_syncs setting).
Well, that error message comes if Dovecot's master binary doesn't recognize the name in "protocol name {". If it's not "imap", "pop3" or "lda" this error comes. So if you had "protocol lda {" in there without any typos or some other weirdness, the only possibility is that the error message didn't come from beta2..
dovecot-1.0.beta2
Does dovecot need to be compiled --without-deliver option to add dovecot-lda later on ? Not very clear on the procedure, maybe that's why it doesn't work.
dovecot-lda compile errors on solaris 9, cc.
CC=cc ./configure --with-dovecot=../dovecot-1.0.beta2
Making all in libsieve
source='comparator.c' object='comparator.o' libtool=no
DEPDIR=.deps depmode=none /bin/bash ../../depcomp
cc -DHAVE_CONFIG_H -I. -I. -I../..
-I/export/home/sho/src/dovecot/dovecot-1.0.beta2
-I/export/home/sho/src/dovecot/dovecot-1.0.beta2/src/lib -I../../src
-g -c comparator.c
"comparator.c", line 149: syntax error before or at: __attribute__
"comparator.c", line 149: warning: undefined or missing type for:
__attribute__
"comparator.c", line 212: warning: statement not reached
"comparator.c", line 213: cannot recover from previous errors
cc: acomp failed for comparator.c
I don't really see why Dovecot would work here differently than UW-IMAP. Indexes shouldn't be the problem.. With 0.99.x I could undestand that it keeps resyncing the whole mbox every time a new mail comes, but 1.0beta should just be looking at the new mails once it has done the initial sync (unless you changed mbox_dirty_syncs setting).
mbox folder with ~10000 messages opens up instantly once indexed, via imap client or web client. once a single message is appended, it takes more then a minute to open the same folder. If message arrives every 30 seconds, the folder can not be opened at all. Any suggestions ? all dirty_sync settings are at their defaults.
On Wed, 2006-02-08 at 22:52 -0500, Lenny wrote:
Well, that error message comes if Dovecot's master binary doesn't recognize the name in "protocol name {". If it's not "imap", "pop3" or "lda" this error comes. So if you had "protocol lda {" in there without any typos or some other weirdness, the only possibility is that the error message didn't come from beta2..
dovecot-1.0.beta2
And dovecot --version says the same thing? :)
Does dovecot need to be compiled --without-deliver option to add dovecot-lda later on ? Not very clear on the procedure, maybe that's why it doesn't work.
No, there are no such checks. It should always accept "protocol lda" section.
dovecot-lda compile errors on solaris 9, cc.
CC=cc ./configure --with-dovecot=../dovecot-1.0.beta2
"comparator.c", line 149: syntax error before or at: __attribute__
Looks like libsieve code assumes GCC is used. Guess I'll have to do something about this..
I don't really see why Dovecot would work here differently than UW-IMAP. Indexes shouldn't be the problem.. With 0.99.x I could undestand that it keeps resyncing the whole mbox every time a new mail comes, but 1.0beta should just be looking at the new mails once it has done the initial sync (unless you changed mbox_dirty_syncs setting).
mbox folder with ~10000 messages opens up instantly once indexed, via imap client or web client. once a single message is appended, it takes more then a minute to open the same folder. If message arrives every 30 seconds, the folder can not be opened at all. Any suggestions ? all dirty_sync settings are at their defaults.
Well, it depends on IMAP client what it does before showing the folder. But setting mbox_very_dirty_syncs=yes should at least help.
participants (2)
-
Lenny
-
Timo Sirainen