Skip to content

v2.4.7

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 16:59
· 237 commits to develop since this release
4385c3e

A patch release of the 2.4 stable line. Cleartext authentication is refused on an unsecured connection by default (GHSA-j9rf-h362-m9q2), STARTTLS listeners gain ssl_mode: required, the Sieve sender logs in to its MTA and verifies it against a named CA, EXAMINE opens a folder read-only, and the chart renders global before and after Sieve scripts. Built with Go 1.27.4.

Before you upgrade

These change what an existing configuration or rollout does. Read them first.

  • Cleartext authentication is refused without TLS by default (#2522, GHSA-j9rf-h362-m9q2). auth_allow_cleartext now defaults to false on every login listener. PLAIN, LOGIN, OAUTHBEARER, XOAUTH2, POP3 USER/PASS and HTTP Basic or Bearer are refused unless the connection is secured: TLS (implicit or after STARTTLS/STLS), a local peer, a peer in general.xclient.trusted_nets, or an accepted PROXY header. IMAP advertises LOGINDISABLED until then. Clients that log in on 143 or 110 without STARTTLS stop working; set auth_allow_cleartext: true on that listener to keep the 2.4.6 behaviour.
  • The Sieve sender logs in and verifies its MTA (#2526). Vacation, redirect, notify and imapsieve mail now logs in with the user and password from sieve.sieve_submission_auth_secret in every container that sends it. Before, the chart read a key nothing set and the sender never logged in. The MTA's certificate is checked against sieve_submission_ssl_ca (new) or the system roots; sieve_submission_ssl_verify (new, default true) turns the check off. An MTA with a certificate from a private CA needs sieve_submission_ssl_ca. Setting the old sieve.submission.authSecret stops the render.
  • A user script that is skipped keeps the message (#2531). A script that does not compile, needs a forbidden extension or is refused gave an empty result, which delivery took as a discard. It now falls back to implicit keep.
  • sieve_max_redirects counts every redirect of a message (#2531), over all its scripts, :copy and :list included; a repeated target is sent once, and one over the limit fails the run, so the message is kept. 0 refuses a script with redirect at upload and skips a stored one at delivery.
  • The chart renders sieve.sieve_global_before and sieve_global_after (#2541). They were in values but never reached the config, so no before or after script ran from the chart. A release that set them now runs them.
  • EXAMINE is read-only (#2543). STORE, EXPUNGE, UID EXPUNGE and MOVE answer NO on a folder opened by EXAMINE, CLOSE expunges nothing, and FETCH sets no \Seen. In 2.4.6 the owner could change and expunge messages through EXAMINE.
  • ManageSieve takes the general PROXY keys (#2524). yarilo-managesieve-login reads general.haproxy.haproxy_trusted_networks and services.managesieve_login.haproxy_protocol. managesieve_login_service.haproxy_trusted_nets and haproxy_protocol still work with a start-up warning; the chart no longer renders them, and components.manageSieveLogin.haproxy_protocol and haproxy_nets left values.yaml.
  • Config schema 29 → 31. Upgrade the chart and the image together; a binary newer than its ConfigMap names the settings it defaulted in a warning at start.
  • Pull the new image onto the backend nodes before helm upgrade, and keep room for one more backend pod, as for 2.4.6. See DEPLOYMENT, "Upgrading the backend StatefulSet".

New

  • ssl_mode: required (#2524) on the four STARTTLS login listeners (IMAP, POP3, Submission, ManageSieve), chart components.<login>.listeners.<listener>.ssl_mode. Before TLS, a local peer, or a PROXY header carrying PP2_CLIENT_SSL, no mechanism is offered, SCRAM included, and Submission answers 530 5.7.0 to everything but EHLO, STARTTLS, NOOP and QUIT. Refused at load together with auth_allow_cleartext: true, on any other listener, or without a certificate.
  • sieve_submission_ssl_verify and sieve_submission_ssl_ca (#2526), as submission_relay_ssl_verify and submission_relay_ssl_ca, for smtps, submissions and starttls.
  • ManageSieve advertises MAXREDIRECTS after authentication when the limit is above 0, and JMAP maxNumberRedirects is 0 for 0 instead of null (#2531).

Fixed

  • IMAP LSUB and LIST (SUBSCRIBED RECURSIVEMATCH) name the parent of a subscription the pattern does not reach: LSUB with \Noselect, LIST with CHILDINFO ("SUBSCRIBED") (RFC 3501 §6.3.9, RFC 5258 §3.5); every subscribed name in a LIST (SUBSCRIBED) answer carries \Subscribed (#2544).
  • IMAP SEARCH: a size key keeps its bound when another key follows it (SMALLER 1 SINCE …), from the go-imap fork (#2543).
  • SMTP (go-smtp fork, #2539): a BDAT refused for a missing RCPT discards its chunk instead of reading it as commands; the line length limit is restored on every exit from BDAT; the client sends a SASL initial response too long for one line as the reply to the first challenge.
  • IMAP FETCH takes 64-bit partial offsets (go-imap fork, #2539).

Operations

  • Go 1.27.4 for CVE-2026-97054, which reaches yarilo through http.MaxBytesReader in jmap-login, the JMAP API and telemetry (#2540).
  • Fork pins on their yarilo-patches heads (go-imap, go-smtp, go-sieve) and module updates: x/oauth2 0.38.0, x/sync 0.25.0, x/sys 0.50.0, x/text 0.44.0, modernc sqlite 1.62.0 (#2539).
  • Trivy ignores GO-2026-5932 in x/crypto until 2026-12-31: it concerns x/crypto/openpgp, which nothing in the module imports (#2533).