feat(container): update ghcr.io/foxcpp/maddy ( 0.7.1 → 0.8.1 ) #3243
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.7.1
->0.8.1
Release Notes
foxcpp/maddy (ghcr.io/foxcpp/maddy)
v0.8.1
: maddy 0.8.1Compare Source
This release includes target.smtp STARTTLS change that originally should have been included in 0.8.0 but was accidentally reverted.
Build attestation
Release artifacts built via GitHub Actions run https://github.com/foxcpp/maddy/actions/runs/12964852891
SLSA Build Attestation for x86_64 linux-musl build: https://github.com/foxcpp/maddy/attestations/4622297
SLSA Build Attestation for Docker image: https://github.com/foxcpp/maddy/attestations/4622340
v0.8.0
: maddy 0.8.0Compare Source
Important changes
Go 1.23
maddy now requires Go 1.23 toolchain to build. "go" command in Go 1.21+
will automatically download newer toolchain if necessary.
SASL LOGIN disabled by default
Obsolete SASL LOGIN mechanism is no longer enabled by default. To re-enable
its support, use
sasl_login
directive in endpoint configuration.STARTTLS plaintext fallback removed in target.smtpIf STARTTLS support is requested for connection in
target.smtp
and the target server does not support STARTTLS message will not be
sent over plaintext connection.
This change does not affect outbound delivery via MX records/port 25.
The default configuration for these is to require TLS (even if the certificate is invalid)
min_tls_level encrypted
in configuration.require_tls
directive is deprecated and will be removed in a future release.attempt_starttls
directive is deprecated and is equivalent tothe newly added
starttls
directive.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_protocol
directive. 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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.