With the options in the upstream dovecot module gone the quota support
and its option now live in our downstream module.
The only behavior change this introduces is not setting a global per
user default instead of the previous 100G per user.
Diabling quota support and setting per user quotas now raises an
assertion:
````
Failed assertions:
- Without quota support enabled, per-user quotas cannot be applied to the following accounts:
- lowquota@example.com
Either remove per user quota settings or re-enable `mailserver.quota.enable`.
````
Create a nicer option structure that deals with the mail storage and its
owner, uid, group and gid. Also includes the directory layout as a
property of how mails are stored..
The "login" prefix makes this option more confusing rather than clearer,
because what other account types are there? LDAP ones for example, but
you can login with those too, so the prefix is pointless.
Drop most of the existing certificate handling, because we're effectively
duplicating functionality that NixOS offers for free with better
design, testing and maintainance than what we could provide downstream.
The remaining two options are to reference an
existing `security.acme.certs` configuration through
`mailserver.x509.useACMEHost` or to provide existing key material via
`mailserver.x509.certificateFile` and `mailserver.x509.privateKeyFile`.
Support for automatic creation of self-signed certificates has been
removed, because it is undesirable in public mail setups.
The updated setup guide now displays the recommended configuration that
relies on the NixOS ACME module, but requires further customization to
select a suitable challenge.
Co-Authored-By: Emily <git@emilylange.de>
Martin Weinelt
Antoine Eiche
Naïm Favier