Good morning,
Thank you so much for your answer. For avoid new logins we can just modify the user auth database, for avoiding, you know, new logins.
The problem is, how to disconnect appropriately an already connected user which for instance, gets connected with IDLE or whatever way of keeping connection alive. Does user_deny.db handle, already logged in users too or just new logins?. The issue we are suffering is with already logged users.
Thanks a lot again :) :) . Any help very appreciated.
Cheers!!
El 2021-10-19 11:50, Dave McMurtrie escribió: Hi, You probably want to use the user_deny.db for this. This is the exact use case for which it was implemented. https://www.cyrusimap.org/imap/reference/admin/sop/userdeny.html hth, Dave On Mon, Oct 18, 2021 at 3:44 AM Egoitz Aurrekoetxea < egoitz@xxxxxxxxxx> wrote:
Good morning,
We have a feature that allows a user to kill all it's sessions. Imagine a cellphone gets stolen. The user could disconnect it's sessions from our interface.
It normally works fine. We just launch a kill TERM to the user's imap/pop processes mainly. But I have seen a couple of times, that after doing that, no user can later connect to it's mailbox. It's like, if something important would become locked... some important database or similar, by that killed processes that obviously as have become killed, won't unlock that hypothetical important database. Have you ever seen a behavior like the commented?.
Perhaps, does Cyrus have another "more elegant" way of logging out a user?.
Best regards,
Cyrus / Info / see discussions + participants + delivery options Permalink
------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Tdfb46db342104c8f-Mc3f7949190d2c0b7279cb642 Delivery options: https://cyrus.topicbox.com/groups/info/subscription
|
