Displaying 3 results from an estimated 3 matches for "afterlogin".
Did you mean:
afterlogic
2017 Jan 25
2
Moving to new password scheme
...t/dovecot-sql.conf.ext
driver = sql
}
protocols = imap
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service imap-login {
inet_listener imaps {
port = 993
ssl = yes
}
}
service imap-postlogin {
executable = script-login /usr/local/etc/dovecot/afterlogin.sh
user = $default_internal_user
}
ssl_cert = </usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem
ssl_key = # hidden, use -P to show it
ssl_protocols = !SSLv2 !SSLv3
userdb {
driver = passwd
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
default_fields = uid=vpopmail gid=vch...
2017 Jan 25
0
Moving to new password scheme
...> service auth {
> unix_listener /var/spool/postfix/private/auth {
> mode = 0666
> }
> }
> service imap-login {
> inet_listener imaps {
> port = 993
> ssl = yes
> }
> }
> service imap-postlogin {
> executable = script-login /usr/local/etc/dovecot/afterlogin.sh
> user = $default_internal_user
> }
> ssl_cert = </usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem
> ssl_key = # hidden, use -P to show it
> ssl_protocols = !SSLv2 !SSLv3
>
> userdb {
> driver = passwd
> }
> userdb {
> args = /etc/dovecot/dovecot-s...
2017 Jan 24
3
Moving to new password scheme
dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably SSHA256-CRYPT, but I want to do this seamlessly without the users having to jump through any hoops.
The users are in mySQL (managed via postfixadmin) and the mailbox record simply stores the hash in the password field. Users access their accounts though