search for: authcaching

2014-12-29 12:47 GMT+01:00 Lazy <lazy404 at gmail.com>: > Hi, > > > I have noticed that during auth cache hits usernames are not updated. > (We use ldap backend > and change username with > user_attrs = uid=user, mailMessageStore=home, > mailQuotaSize=quota_rule=*:bytes=%$ > > cold cache > > lmtp(14414): Debug: auth input: testmon_testmon >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 29 Dec 2014, Lazy wrote: > > I have noticed that during auth cache hits usernames are not updated. > (We use ldap backend > and change username with > user_attrs = uid=user, mailMessageStore=home, > mailQuotaSize=quota_rule=*:bytes=%$ > > cold cache > > lmtp(14414): Debug: auth input: testmon_testmon >

Hello, setting auth_cache_size to nonzero enables caching of authentication data. The cache hitrate may be logged by sending SIGUSR2 to dovecot/auth process. Is it possible that dovecot logs statistics on regular intervals ? ( like http://www.postfix.org/postconf.5.html#anvil_status_update_time ) Andreas -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 N?rnberg | Telefon +49 911 319-0

2015-01-09 9:16 GMT+01:00 Steffen Kaiser <skdovecot at smail.inf.fh-brs.de>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Mon, 29 Dec 2014, Lazy wrote: > >> >> I have noticed that during auth cache hits usernames are not updated. >> (We use ldap backend >> and change username with >> user_attrs = uid=user, mailMessageStore=home,

Hi, I have noticed that during auth cache hits usernames are not updated. (We use ldap backend and change username with user_attrs = uid=user, mailMessageStore=home, mailQuotaSize=quota_rule=*:bytes=%$ cold cache lmtp(14414): Debug: auth input: testmon_testmon home=/vmail/te/testmon_testmon quota_rule=*:bytes=104857600 lmtp(14414): Debug: changed username to testmon_testmon lmtp(14414): Debug:

...[squirrelmail]. I've since read about the dovecot proxying features and it seems to make sense to replace predition in that above scenario. I'm unclear about the benefits of the auth_cache and how it compares to the using imapproxy in front of webmail client? Does it make sense to have authcaching switched on in the proxy and not on the backend server? (Doesn't the authentication just have to happen on the backend server?) Are there any performance benefits to using a proxying server, or is it just for splitting mailstores? thanks for your work, Dan Poltawski -------------- next part...