Repository navigation
maddy 0.8.0
#743
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Important changes
SASL LOGIN disabled by default
Obsolete SASL LOGIN mechanism is no longer enabled by default. To re-enable
its support, use
sasl_logindirective in endpoint configuration.STARTTLS plaintext fallback removed in target.smtp
If STARTTLS support is requested for connection in
target.smtpand the target server does not support STARTTLS message will not be
sent over plaintext connection.
require_tlsdirective is deprecated and will be removed in a future release.attempt_starttlsdirective is deprecated and is equivalent tothe newly added
starttlsdirective.STARTTLS plaintext fallback in target.remote is more strict
If STARTTLS command is rejected by the remote server or connection error
happens before STARTTLS completes (that is, no TLS handshake takes place)
then unauthenticated TLS or plaintext fallback is no longer attempted.
New features
PROXY protocol support
maddy now supports HAProxy PROXY protocol for IMAP and SMTP endpoints
via
proxy_protocoldirective. Both v1 (text) and v2 (binary) versionsare supported. There is also additional support for second TLS layer
between proxy and maddy that can be configured using proxy_protocol.tls
directive.
RFC 2136 libdns provider
Built-in ACME client can be configured to set DNS-01 challenge records
using RFC 2136 protocol.
Support is not compiled-in by default and should be enabled using
libdns_rfc2136 build tag.
ACME-DNS libdns provider
Built-in ACME client can not be configured to delegate DNS-01 challenge
to the https://github.com/joohoi/acme-dns server.
Support should be enabled via libdns_acmedns build tag.
Bug fixes
Misc improvements
Build attestation
This discussion was created from the release maddy 0.8.0.
All reactions