Hi,
I upgraded to 20150213 (f10725a5eed8+). I chose LDAP as the authentication
source for Dovecot.
Compilation succeeds. Starting dovecot from command line :
/usr/local/sbin/dovecot -c /usr/local/etc/dovecot/
The error log contains :
"dovecot: auth: Fatal: No passdbs specified in configuration
Sorry, I forgot to specify my workload :
./imaptest-1.0.0/src/imaptest secs=300 clients=800 seed=123
userfile=/tmp/userlist_imaptest no_tracking mbox=/tmp/dovecot-crlf
with dovecot-crlf : http://www.dovecot.org/tmp/dovecot-crlf
Kind regards, rub
2015-01-14 15:50 GMT+01:00 rub zorghy :
>
Hi,
The measurements were created under the following conditions :
• operating system : Red Hat Enterprise Linux Server release 6.6 (Santiago)
kernel in version 2.6.32-504.el6.x86_64
• virtual server (VMware) with an Intel(R) Xeon(R) 4vCPU E5649 x 2,526 GHz
(2 cores per virtual socket) and 4 GB R
Hi,
Timo Sirainen wrote (May 19, 2010 1:50:34 am) :
"When a connection from a newly seen user arrives, it gets assigned to a
mail server according to a function:
host = vhosts[ md5(username) mod vhosts_count ]"
This hash function is it still used as it is without modification ?
My another ques
Hi Alessio,
Thank you very much for your detailed explanation.
gdrub
2014-12-01 18:28 GMT+01:00 Alessio Cecchi :
>
> Il 01/12/2014 17:11, rub zorghy ha scritto:
>
>> Why Dovecot Director server isn't used to perform this without Dovecot
>> proxy ? Thus, the loa
Hi,
Dovecot Director is used to keep a temporary user -> Dovecot backend server
mapping. So, Director decides which backend handles each user and the user
is always redirected to the same server. All user data is stored in shared
storage (NFS).
The Dovecot presentation featured during this webinar
