mirror of
https://blitiri.com.ar/repos/chasquid
synced 2025-12-18 14:47:03 +00:00
17b7bbe9c6
dovecot support has been around for a release, has decent testing and seems stable enough to remove the "experimental" qualifier.
53 lines
1.2 KiB
Markdown
53 lines
1.2 KiB
Markdown
|
|
# Dovecot integration
|
|
|
|
As of version 0.04 (2018-02), [chasquid] has integration with [dovecot] for
|
|
authenticating users.
|
|
|
|
This means that chasquid can ask dovecot to authenticate users, instead/in
|
|
addition to having its own per-domain user databases.
|
|
|
|
|
|
## Configuring dovecot
|
|
|
|
The following needs to be added to the Dovecot configuration, usually in
|
|
`/etc/dovecot/conf.d/10-master.conf`:
|
|
|
|
```
|
|
service auth {
|
|
unix_listener auth-chasquid-userdb {
|
|
mode = 0660
|
|
user = chasquid
|
|
}
|
|
unix_listener auth-chasquid-client {
|
|
mode = 0660
|
|
user = chasquid
|
|
}
|
|
}
|
|
```
|
|
|
|
If chasquid is running under a different user, adjust the `user = ` lines
|
|
accordingly.
|
|
|
|
This lets chasquid issue authentication requests to dovecot.
|
|
|
|
|
|
## Configuring chasquid
|
|
|
|
Add the following line to `/etc/chasquid/chasquid.conf`:
|
|
|
|
```
|
|
dovecot_auth: true
|
|
```
|
|
|
|
That should be it, because chasquid will "autodetect" the full path to the
|
|
dovecot sockets, by looking in the usual places (tested in Debian, Ubuntu, and
|
|
CentOS).
|
|
|
|
If chasquid can't find them, the paths can be set with the
|
|
`dovecot_userdb_path` and `dovecot_client_path` options.
|
|
|
|
|
|
[dovecot]: https://dovecot.org
|
|
[chasquid]: https://blitiri.com.ar/p/chasquid
|