search for: auth_cach

Hi , just to make clear short question does auth_cache... help with downing sql lookups http://wiki2.dovecot.org/Authentication/Caching isnt clear to me for sql to me if yes are there real world recommanded settings lets say for a 5000 users server and where password changes should be noticed asap -- Best Regards MfG Robert Schetterer Germany/Munic...

Hi, I have: auth_cache_size = 4096 auth_cache_ttl = 3600 I use Thunderbird connecting to my Dovecot IMAP server 1.1rc1. I click on five folders and close Thunderbird. This is my log: dovecot: Feb 27 17:26:56 Info: Dovecot v1.1.rc1 starting up dovecot: Feb 27 17:26:56 Info: auth-worker(default): mysql: Connect...

When you set auth_cache_size to a value greater than zero, it breaks the master password feature in Dovecot. It appears that during a cache hit, Dovecot attempts to query the userdb for use the master user's home directory and other settings, rather than querying for the userdb settings of the user that the master w...

...module for now). For a single webmail connection par login, it work, thanks to cache_key using client's IP. But for multiple use of the same login in the webmail, there are more than one 'password' valid at a time? What may be the 'correct' solution: - patching auth-cache.c (auth_cache_lookup function ?) - writing a different login backend ? - ??? Hope I'm clear enough? -- geoffroy desvernay Ecole Centrale de Marseille -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: O...

I have my quota limits stored in userdb and auth_cache enabled (default settings). When I change the quota limit the old limit is still cached for the user for another hour. Is there any way to prevent this from happening? Thanks -- Tom

This patchset add support for One-Time-Password authentication mechanisms, both S/Key (RFC 1731) and OTP (RFC 2444) are implemented. Tested with mutt (uses cyrus sasl library for authentication). Patches were made against CVS HEAD. Please take a look. Add auth_cache_remove() function which will be used by OTP code to evict old entries from auth cache. diff -urdpNX /usr/share/dontdiff -x Makefile dovecot.vanilla/src/auth/auth-cache.c dovecot/src/auth/auth-cache.c --- dovecot.vanilla/src/auth/auth-cache.c 2006-06-23 13:42:22.122508080 +0400 +++ dovecot/src/aut...

...hing I would like to avoid. --- Tom On 2017-02-06 14:29, Urban Loesch wrote: > You can flush the cache with: "doveadm auth cache flush $USER" > > Regards > Urban > > > Am 06.02.2017 um 13:59 schrieb Tom Sommer: >> I have my quota limits stored in userdb and auth_cache enabled >> (default settings). >> >> When I change the quota limit the old limit is still cached for the >> user for another hour. Is there any way to prevent this from >> happening? >> >> Thanks >>

...quota in SQL, the change is not reflected in Dovecot immediately so quota_warning is still triggered on some occasions. I think it's because the quota is stored in userdb, and there is no way to flush userdb cache? Is there a way to flush userdb entries? What controls userdb cache TTL/size? auth_cache entries? I can't seem to find any documentation on this, sadly :( Thanks -- Tom

Has anybody noticed this behavior when using maildir quota with Version 1.2.4: # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.3 xfs My default configurations quota configurations: plugin: quota: maildir:User quota quota_rule: *:storage=2G Customized Use Configurations at the Mysql level: user_query = SELECT 5000 AS uid,5000 AS gid,'/vmail/%d/%n'

I was going to ask how much space I should allocate for auth_cache_size - but decided to read the wiki first. Now I'll be more specific - Wiki says about 50 bytes per passdb, and up to 200 bytes for userdb - so my arithmetic says each combined entry needs 250 bytes budgeted. Assuming that's correct, I need some clarification. Let's start small....

...ith mail_log plugin. - Changing message flags was more or less broken in rc19 - ACL plugin still didn't work without separate control directory - Some mbox handling fixes, including fixing an infinite loop - Some index file handling fixes - maildir quota: Fixed a file descriptor leak - If auth_cache was enabled and userdb returned "user unknown" (typically only deliver can do that), dovecot-auth crashed. - mail_log plugin didn't work with pop3 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Si...

...ith mail_log plugin. - Changing message flags was more or less broken in rc19 - ACL plugin still didn't work without separate control directory - Some mbox handling fixes, including fixing an infinite loop - Some index file handling fixes - maildir quota: Fixed a file descriptor leak - If auth_cache was enabled and userdb returned "user unknown" (typically only deliver can do that), dovecot-auth crashed. - mail_log plugin didn't work with pop3 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Si...

...3 - Re-apply permissions 4 - Remove user index folder After I do that, users cannot authenticate unless I restart dovecot, process that I would like to avoid. Can you guys give a tip on what I need to change to avoid this last problematic step? After the restart, everything works. Does the auth_cache feature also store the homedir location? System: CentOS 7 Versions: dovecot-pigeonhole-2.2.10-8.el7.x86_64 dovecot-2.2.10-8.el7.x86_64 Doveconf -n: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-693.5.2.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) auth_cache_...

...ystems without it being rebuilt. * Added libmysqlclient workaround to conflicting sha1_result symbol, which caused Dovecot to fail logging into MySQL. + dovecot.index.cache file opening is delayed until it's actually needed. This reduces disk accesses a bit with eg. STATUS commands. + auth_cache: Try to handle changing passwords automatically: If password verification fails, but the last one had succeeded, don't use the cache. This works only with plaintext auth. - dovecot.index.cache: We didn't properly detect if some fields were different length than we expected, which...

...ystems without it being rebuilt. * Added libmysqlclient workaround to conflicting sha1_result symbol, which caused Dovecot to fail logging into MySQL. + dovecot.index.cache file opening is delayed until it's actually needed. This reduces disk accesses a bit with eg. STATUS commands. + auth_cache: Try to handle changing passwords automatically: If password verification fails, but the last one had succeeded, don't use the cache. This works only with plaintext auth. - dovecot.index.cache: We didn't properly detect if some fields were different length than we expected, which...

...ver untested, hopefully didn't break LDAP code completely.. - %w variable in dovecot-auth contains password. Can be used to do eg.: password_query = select null as password from users where userid = '%u' and password = password('%w') - syslog_facility setting And fixes: - auth_cache was quite broken - adding keywords caused sometimes assert-crash - If login_greeting_capability = yes we could have sent the capability before dovecot-auth returned what auth mechanisms were available, forcing clients to use plaintext authentication - Lots of mbox fixes again.. - userdb prefet...

> Old server: > * Ubuntu 10.04.4 LTS > * Dovecot 2.1.13 > * Maildir++ > * Local auth via passwd/shadow files > > New server: > * Debian GNU/Linux 8.6 > * Dovecot 2.2.13 > * Maildir++ > * Quotas enabled > * LDAP > > Basically what's happening is that users are seeing large delays when > navigating between different IMAP folders. So, for example, user

You can flush the cache with: "doveadm auth cache flush $USER" Regards Urban Am 06.02.2017 um 13:59 schrieb Tom Sommer: > I have my quota limits stored in userdb and auth_cache enabled (default settings). > > When I change the quota limit the old limit is still cached for the user for another hour. Is there any way to prevent this from happening? > > Thanks >

...not correctly handled and leads to situation in > which last mailbox/home directory is used for the replication :( It sounds to me like a userdb lookup changes the username during a dict failure. Although I can't really think of how that could happen. The only thing that comes to my mind is auth_cache, but in that case I'd expect the same problem to happen even when there aren't dict errors. For testing you could see if it's reproducible with: - get random username - do doveadm user <user> - verify that the result contains the same input user Then do that in a loop rapid...

http://dovecot.org/test/ Nothing big this time: - Added configurable logging for login process. Added configurable pop3 logout string. Based on a patch by Andrey Panin. - mysql auth: dovecot-auth worker processed kill themselves after 10min idle time - fixed auth_cache crashing with sql/ldap backends (or was it only with mysql?) - fixed pop3 hang (finally I hope? :) - fixed mbox assert-crash about the file size being unexpected - Keyword resets were written using sequences to transaction log, which caused keyword breakages. - pop3: RSET command wasn't wo...