diff options
| author | Martin Weinelt <hexa@darmstadt.ccc.de> | 2025-11-17 20:37:04 +0100 |
|---|---|---|
| committer | Martin Weinelt <hexa@darmstadt.ccc.de> | 2025-11-17 20:52:23 +0100 |
| commit | a38229c0cb835f4286527ece99abd3a37b0bee05 (patch) | |
| tree | 3d44b8b91db77950acafc06278d1e09c451dc946 /pkgs/development/python-modules/python-openstackclient | |
| parent | 1f17bc07537bb214278079c9584813b5392b42fb (diff) | |
Revert "nixos/postfix-tlspol: make tlsrpt depend on tlsrpt service"
This reverts commit 9ccec77537e72c1f7e792e838e99c1f0d7692850.
Per the author of postfix-tlspol in
https://github.com/NixOS/nixpkgs/pull/456728#issuecomment-3536706358
> QUERYwithTLSRPT should be used when the installed Postfix version is
> 3.10 or newer, regardless of the state of the TLSRPT option in the
> Postfix configuration. Especially Postfix 3.10.5 and later use the
> additional data provided by postfix-tlspol to find the correct MX
> domains to connect to MTA-STS-protected mail destinations.
>
> If you use QUERY with Postfix 3.10.5+, Postfix will use the legacy
> way of DNS MX lookup for the domain, which theoretically can differ
> from the hosts provided by the MTA-STS policy (but usually should be
> the same).
>
> The user can still disable TLSRPT in the Postfix configuration without
> side-effects.
Diffstat (limited to 'pkgs/development/python-modules/python-openstackclient')
0 files changed, 0 insertions, 0 deletions