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
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 >
I know, but I'm changing the quota in dict:sql so running commands on the mailserver itself it something 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 >>