2020-11-12 12:40:52 +01:00
## Fully supported hashing methods
2020-11-12 10:20:00 +01:00
The most current mailcow fully supports the following hashing methods.
The default hashing method is written in bold:
- **BLF-CRYPT**
2020-12-07 07:53:16 +01:00
- SSHA
2020-11-12 10:20:00 +01:00
- SSHA256
- SSHA512
The methods above can be used in `mailcow.conf` as `MAILCOW_PASS_SCHEME` value.
## Read-only hashing methods
2021-02-11 09:56:11 +01:00
The following methods are supported **read only** .
If you plan to use SOGo (as per default), you need a SOGo compatible hashing method. Please see the note at the bottom of this page how to update the view if necessary.
With SOGo disabled, all hashing methods below will be able to be read by mailcow and Dovecot.
2020-11-12 10:20:00 +01:00
2021-02-11 09:56:11 +01:00
- ARGON2I (SOGo compatible)
- ARGON2ID (SOGo compatible)
2021-02-11 09:48:42 +01:00
- CLEAR
- CLEARTEXT
2021-02-11 09:56:11 +01:00
- CRYPT (SOGo compatible)
2021-02-11 09:48:42 +01:00
- DES-CRYPT
2021-02-11 09:56:11 +01:00
- LDAP-MD5 (SOGo compatible)
- MD5 (SOGo compatible)
- MD5-CRYPT (SOGo compatible)
- PBKDF2 (SOGo compatible)
- PLAIN (SOGo compatible)
2021-02-11 09:48:42 +01:00
- PLAIN-MD4
2020-11-12 10:20:00 +01:00
- PLAIN-MD5
2021-02-11 09:48:42 +01:00
- PLAIN-TRUNC
2021-02-11 09:56:11 +01:00
- SHA (SOGo compatible)
- SHA1 (SOGo compatible)
- SHA256 (SOGo compatible)
- SHA256-CRYPT (SOGo compatible)
- SHA512 (SOGo compatible)
- SHA512-CRYPT (SOGo compatible)
- SMD5 (SOGo compatible)
2020-11-12 10:20:00 +01:00
That means mailcow is able to verify users with a hash like `{PLAIN-MD5}1a1dc91c907325c69271ddf0c944bc72` from the database.
The value of `MAILCOW_PASS_SCHEME` will _always_ be used to encrypt new passwords.
---
> I changed the password hashes in the "mailbox" SQL table and cannot login.
A "view" needs to be updated. You can trigger this by restarting sogo-mailcow: `docker-compose restart sogo-mailcow`
