Dear SOGo Staff,
I'm using SOGo 2.2.16 in a large system. I haven't upgraded it,
because on this list I saw some information about problems with
calendar after an upgrade.
Now I'm planning upgrade to newest 2.3 version and I have some
doubts conected with it.
I know I have to run the
W dniu 31.03.2017 o 12:41, Mikhail Emelchenkov (mikh...@emelchenkov.pro)
pisze:
The very first idea: centralised password management. Changing password
will be performing by providing an old password and a new one. New
password will be stored to LDAP/Database, and both old and new will be
send
W dniu 31.03.2017 o 09:45, Mikhail Emelchenkov (mikh...@emelchenkov.pro)
pisze:
Is any kind of storage encryption planning to implement in SOGo? I think
about this one: encrypt everything (mail, contacts, calendar) with a key
encrypted with user password which a user send at authentication time.
W dniu 24.04.2018 o 16:51, Sebastián Meyer (sebast...@indomitux.com) pisze:
I have a couple of compromissed webmail accounts, passwords wheren't
easy to guess.
I'd like to add an increasing delay for failed logins and a captcha, is
it possible?
You can do that by these global settings:
W dniu 12.05.2020 o 13:58, Christian Mack
(christian.m...@uni-konstanz.de) pisze:
Am 12.05.20 um 05:39 schrieb Jose David Bravo A
(jbr...@colombiahosting.com.co):
I'm using sogo 4.3 but my users are able to set passwords very weak passwords,
like 123. Is there any way to restrict the creation
