YariloMail 2.4.7: TLS before passwords, a Sieve sender that logs in
16 November 2026
YariloMail 2.4.7 is a release of the 2.4 stable line. It closes a security advisory, GHSA-j9rf-h362-m9q2: by default, the IMAP, POP3 and ManageSieve login proxies offered and accepted passwords before STARTTLS, on a connection that was not encrypted. Read "Before you upgrade" first: clients that send a password on port 143 or 110 without STARTTLS are now refused.
Security
- No password before TLS.
auth_allow_cleartextnow defaults to off. PLAIN, LOGIN, POP3 USER/PASS and HTTP Basic are accepted only on a secured connection: TLS, a local peer, a trusted network or an accepted PROXY header. Until then IMAP advertisesLOGINDISABLEDand offers no password mechanism, and every refusal is logged. ssl_mode: requiredon the IMAP, POP3, Submission and ManageSieve STARTTLS listeners: no authentication at all, SCRAM included, until the connection is encrypted. Submission answers530 5.7.0to everything but EHLO, STARTTLS, NOOP and QUIT.- Go 1.27.4, for CVE-2026-97054 in the Go HTTP server.
Sieve
- The Sieve sender logs in. Vacation replies, redirects, notifications and imapsieve mail now authenticate to the MTA from every container that sends them, and the MTA's certificate is checked against a CA you name with
sieve_submission_ssl_ca. - Global scripts from the Helm chart.
sieve_global_beforeandsieve_global_afterwere accepted in the values but never reached the configuration. They now run, so a site-wide rule such as filing spam into Junk can be set from the chart. - No silent discards. A user script that does not compile or is refused now keeps the message instead of dropping it.
sieve_max_redirectscounts every redirect of a message across all its scripts; a repeated address is sent once, and a message over the limit is kept.
IMAP
- EXAMINE is read-only, as RFC 9051 requires: STORE, EXPUNGE and MOVE are refused, CLOSE expunges nothing, and reading a message does not mark it
\Seen. - LSUB and LIST (SUBSCRIBED RECURSIVEMATCH) name the parent folder of a subscription the pattern does not reach, so clients that show only subscribed folders no longer lose a subscribed subfolder.
- SEARCH keeps a size bound when another key follows it, and FETCH takes large partial offsets.
Before you upgrade
- Cleartext passwords need TLS. A client that logs in on 143 or 110 without STARTTLS stops working. Move it to 993/995 or STARTTLS, or set
auth_allow_cleartext: trueon that listener to keep the 2.4.6 behaviour. - The Sieve sender verifies its MTA. An MTA with a certificate from a private CA needs
sieve_submission_ssl_ca. - EXAMINE no longer writes. A client that changed flags or expunged through EXAMINE gets
NOand has to use SELECT. - Config schema 29 → 31: upgrade the chart and the image together. Pull the new image onto the backend nodes before
helm upgrade, and keep room for one more backend pod.
Read the release notes before you run helm upgrade: they list every change that affects an existing configuration.
How it was tested
The release image passed a full acceptance run on the stand, then a window against 2.4.6 in the same slot, with 2.4.6 measured both before and after it: 2.4.7 stayed within the spread between the two 2.4.6 runs or above it on every storage format, with no client errors. A rollback from 2.4.7 to 2.4.6 on the same store kept every message readable.
Get it
- Release and notes: github.com/yarilomail/yarilo/releases/tag/v2.4.7
- Image:
0kaba0/yarilo:2.4.7on Docker Hub - Helm chart:
helm install yarilo oci://ghcr.io/yarilomail/charts/yarilo --version 2.4.7 - Documentation for this release: doc.yarilomail.org/2.4.7; the latest release is always at doc.yarilomail.org