treewide: fix typos and other minor issues
This commit is contained in:
@@ -12,7 +12,7 @@ anything works, as it is simply a folder with plenty of files in it. If
|
||||
your backup solution does not preserve the owner of the files don’t
|
||||
forget to ``chown`` them to ``virtualMail:virtualMail`` if you copy them
|
||||
back (or whatever you specified as ``vmailUserName``, and
|
||||
``vmailGoupName``).
|
||||
``vmailGroupName``).
|
||||
|
||||
If you enabled ``enableManageSieve`` then you also may want to backup
|
||||
``/var/sieve`` or whatever you have specified as ``sieveDirectory``.
|
||||
|
||||
+1
-1
@@ -48,7 +48,7 @@ recommended to move indices in a different location, such as
|
||||
When the value of the ``indexDir`` option is changed, all dovecot
|
||||
indices needs to be recreated: clients would need to resynchronize.
|
||||
|
||||
Indexation itself is rather resouces intensive, in CPU, and for emails with
|
||||
Indexation itself is rather resource intensive, in CPU, and for emails with
|
||||
large headers, in memory as well. Initial indexation of existing emails can take
|
||||
hours. If the indexer worker is killed or segfaults during indexation, it can
|
||||
be that it tried to allocate more memory than allowed. You can increase the memory
|
||||
|
||||
@@ -38,8 +38,8 @@ You can then run the testsuite via
|
||||
|
||||
$ nix flake check -L
|
||||
|
||||
Since Nix doesn't garantee your machine have enough resources to run
|
||||
all test VMs in parallel, some tests can fail. You would then haev to
|
||||
Since Nix doesn't guarantee your machine have enough resources to run
|
||||
all test VMs in parallel, some tests can fail. You would then have to
|
||||
run tests manually. For instance:
|
||||
|
||||
::
|
||||
|
||||
@@ -35,14 +35,14 @@ NixOS 25.11
|
||||
1024 bit keys should not be considered valid any longer.
|
||||
- IMAP access over port ``143/tcp`` is now default disabled in line
|
||||
with `RFC 8314 4.1`_. Use IMAP over implicit TLS on port ``993/tcp``
|
||||
instead. If you still require this feature you can reenable it using
|
||||
instead. If you still require this feature you can re-enable it using
|
||||
``mailserver.enableImap``, but it is scheduled for removal after the 25.11
|
||||
release.
|
||||
- SMTP server and client now support and prefer a hybrid key exchange
|
||||
(X25519MLKEM768)
|
||||
- SMTP access over STARTTLS on port ``587/tcp`` is now default disabled in line
|
||||
with `RFC 8314 3.3`_. If you still require this feature you can renable it using
|
||||
``mailserver.enableSubmission``.
|
||||
with `RFC 8314 3.3`_. If you still require this feature you can re-enable it
|
||||
using ``mailserver.enableSubmission``.
|
||||
- DMARC reports are now sent with the ``noreply-dmarc`` localpart from the
|
||||
system domain.
|
||||
- DANE and MTA-STS are now validated for outgoing SMTP connections using
|
||||
|
||||
@@ -94,7 +94,7 @@ With an nginx reverse-proxy
|
||||
|
||||
If you have a secured nginx reverse proxy set on the host, you can use it to expose the socket.
|
||||
**Keep in mind the UI is unsecured by default, you need to setup an authentication scheme**, for
|
||||
exemple with `basic auth <https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/>`_:
|
||||
example with `basic auth <https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/>`_:
|
||||
|
||||
.. code:: nix
|
||||
|
||||
|
||||
Reference in New Issue
Block a user