mixandClaude Opus 5.5
1c6e04b7d3
test / test (push) Canceled after 0s
The runtime base is debian:trixie-slim, the build stage golang:1.26-trixie:
Postfix 3.10.13 with upstream's 2026 security fixes up to the August
batch, libmilter 8.18.1, OpenSSL 3.5. Every citation of another program in
code, scripts and documents was re-read against the trixie sources
(dev/upstream; bookworm's kept in dev/upstream-bookworm) and updated;
development.md's cited-package table holds the trixie versions.
What the re-reading changed in behaviour:
- logtail: reject lines with sasl_method/sasl_username/sasl_sender
(smtpd_check.c:1019-1026); cleanup's "removed (canceled)" forgets a
port-25 id (cleanup_api.c:363-364).
- internal/postfix/retry.go reads postconf's stdout only: since 3.9 a
deprecated-parameter warning on stderr made one value too many and the
panel fell back to the compiled-in retry policy.
- logrotate-loop.sh: logrotate 3.22 exits 1 when it ignores a config;
the loop refuses on that output whatever the status.
- postfix-config.sh: cyrus_sasl_config_path set explicitly (bookworm's
07_sasl_config.diff is gone); maillog_file_permissions=0640; mynetworks
explicit; Dockerfile: SYNC_CHROOT= in /etc/default/postfix,
opendkim-tools dropped, openssl named, systemd-standalone-sysusers so
cron does not bring the whole of systemd.
- The selfpost group is 10998, outside the system range 100-999: in
trixie a package took 998 and the build failed (owner's decision:
a conflict-free id, the distribution's own ids untouched). The
entrypoint hands /data back by name when the user or the group differs.
Guide, backup refusal text, help (design commit 68ec8b2), e2e.
- smtpd_hide_client_session=yes on smtps and submission (owner's
decision): Received: names no client, TLS, login or protocol; port 25
keeps the full header. e2e checks both.
- test/upstream/opendkim-probe.sh makes keys with openssl genrsa.
Tests: on the server, make e2e exit 0 (674 s, the image built on trixie),
go vet + go test 27 packages ok. CHANGELOG [Unreleased], guide,
architecture.md, security.md, roadmap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
23 lines
1.2 KiB
Bash
23 lines
1.2 KiB
Bash
#!/bin/sh
|
|
# The reload the panel asks supervisord for (program postfix-reload,
|
|
# build/supervisord.conf; internal/supervisor RunOnce reads its exit status).
|
|
#
|
|
# Exit 75 says no Postfix master runs - it is stopped, or still in its start
|
|
# behind the milter wait (build/postfix-wrapper.sh) - and the master that
|
|
# starts next reads the files as they are now, so the panel takes that as
|
|
# done. Anything else is "postfix reload" itself: 0, or its failure (Postfix
|
|
# 3.10.13, conf/postfix-script:266-279, "reload": exit 1 when not running or
|
|
# when postsuper fails; src/postfix/postfix.c, a main.cf it cannot read). "master
|
|
# -t" exits 0, silently, while no master holds the lock (src/master/master.c:495-499,
|
|
# test_lock). A master that stops between the two is a failure the panel
|
|
# reports - the rarer mistake (review of stage 2c, F5). Since Postfix 3.8 the
|
|
# reload also writes "refreshing the Postfix mail system" to stderr, which
|
|
# goes to the container's log (postfix-wrapper.sh, the note on 3.8's stderr
|
|
# logging); the panel reads only the exit status.
|
|
d=$(postconf -h daemon_directory) || exit 1
|
|
if "$d/master" -t 2>/dev/null; then
|
|
echo "postfix-reload: Postfix is not running; its start reads the files" >&2
|
|
exit 75
|
|
fi
|
|
exec /usr/sbin/postfix reload
|