similar to: Userdb authentication cache

Hello, I tried the v1.0 test of dovecot, because it should make the directories for me. I configured it and installed it. The old one is still there, but I shut it down to test the other version. When I start the new v1.0 test of dovecot i get the following message in my log: Jun 6 13:33:08 APOLLO dovecot: Dovecot v1.0-test72 starting up Jun 6 13:33:09 APOLLO dovecot: Auth process died too

I'm trying Dovecot v1.0-test43 with ldap authentication but can't seem to make it work. I'm getting the following errors in the log: dovecot: Sep 16 19:50:09 Info: Dovecot v1.0-test43 starting up dovecot: Sep 16 19:50:10 Error: Auth process died too early - shutting down What can I do to see where the error is? I have this configuration working with dovecot 0.99.xx . And if I

New branch created to CVS: branch_1_0 It's going to stabilize into v1.0 Dovecot, hopefully somewhat soon. I'll start adding new larger features into HEAD, so you might want to switch to branch_1_0 if you're currently using Dovecot from CVS. You can do this with: cvs up -r branch_1_0 The nightly snapshots are from branch_1_0, at least for now. -------------- next part --------------

New branch created to CVS: branch_1_0 It's going to stabilize into v1.0 Dovecot, hopefully somewhat soon. I'll start adding new larger features into HEAD, so you might want to switch to branch_1_0 if you're currently using Dovecot from CVS. You can do this with: cvs up -r branch_1_0 The nightly snapshots are from branch_1_0, at least for now. -------------- next part --------------

Backported from CVS HEAD to branch_1_0. You can get it as a patch from http://dovecot.org/patches/1.0/quota-rewrite.diff New features include support for multiple quota roots, so you could have eg. per-user quota and a larger domain quota (although no backend actually supports this yet..). The more important feature is that you can configure specific mailboxes to have a bit more space available

This line in configure.in src/plugins/mail-log/Makefile refers to a non existing direcory in the branch_1_0 tree, which breaks build. ciao Luca

Somehow I doubt there are any Dovecot setups left that unknowingly have this problem, but it still counts as a security hole. The possibility to cause this problem exists in Dovecot v1.0.rc11 and later. If you use: 1. passdb ldap with settings: - auth_bind = yes - auth_bind_userdn = no - base containing %variables required for unique user identification, e.g. base = dc=%d,dc=org -

As you can probably guess from my today's burst of activity, I'm no longer extremely busy. Actually it looks like for the next 3-4 weeks I don't have anything especially time consuming to do. So it's time to get Dovecot v1.0 released :) I've now read all the mails from this list again, and it looks like pretty much the only problems with rc10 was the mbox assert crash, which

Somehow I doubt there are any Dovecot setups left that unknowingly have this problem, but it still counts as a security hole. The possibility to cause this problem exists in Dovecot v1.0.rc11 and later. If you use: 1. passdb ldap with settings: - auth_bind = yes - auth_bind_userdn = no - base containing %variables required for unique user identification, e.g. base = dc=%d,dc=org -

I wasted too much time today doing this, but they do show a few interesting things: 1) mmap_disable=yes is faster than mmap_disable=no. I didn't expect this. I'm not yet sure why this is, but possibly because then it updates the mail index by reading the changes from dovecot.index.log, instead of reopening and re-mmaping dovecot.index. At least that's the biggest difference between

Hi Guys, We have: auth_cache_size = 2048 #Kb auth_cache_ttl = 900 #life of the cache Seems to work well (though haven't tried looking at stats). Only problem is that every so often, one of our new users tries to log in quickly before the account is marked (in a db) as 'active'. They use the right password but the sql query fails because the active flag is not yet set. This

Hello, first sorry for this question. I already found many threads about this problem including a thread in this list from August 2010, but nothing helped :( Here is the error: 2010-09-20 06:28:04 lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules/ 2010-09-20 06:28:04 lda: Debug: Module loaded: /usr/lib/dovecot/modules//lib90_sieve_plugin.so 2010-09-20 06:28:04 lda: Error:

Some new features in CVS HEAD are: - v1.0 saves most of the data to dovecot.index.cache only when the client is FETCHing the messages. With mboxes the message headers are saved while parsing the mbox, which is almost the same thing. With CVS HEAD the dovecot.index.cache file is updated already when the new messages are being saved (with deliver or IMAP APPEND). This avoids reading the message

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them

After v1.0 is released, I can finally get back to sane version numbers. But any comments on which one is better: a) Postfix-style: "1.1.UNSTABLE.YYYYMMDD" -> 1.1.0 (stable) b) Odd-even numbering: 1.1.x (unstable) -> 1.2.0 (stable) With a) style the releases could be done by simply copying a nightly snapshot to releases/ directory and announcing the changes since the last

Hi all, I'm using 1.0.beta3 and having problems using userdb prefetch in conjuction with passdb sql. Here are my mail logs when I log to virtual account "testuser at mydomain.com" by doing "telnet localhost 143": Mar 26 15:15:47 imapserver dovecot: Dovecot v1.0.beta3 starting up Mar 26 15:15:49 imapserver dovecot: auth-worker(default): mysql: Connected to (null) (mail)

Any way to minimize the number of sql statements that dovecot do? (and I tried adding userdb prefetch { } but number of sql calls are still the same) Am I doing something wrong or? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bj?rn T Johansen btj at havleik.no

Hi! I'm testing 1.1, and have some questions. (How) Can I override the default maildir++ quota setting (I mean quota_rule) in the userdb, so that one won't have quota at all. Right now I'm setting a very high limit in the userdb with quota_rule=*:storage=99G in the extra field. Prior to 1.1 I was using 1.0 and had fs quota. I've had set up dovecot so that the indexes were

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/