proto/ldap_table | 2 1 + 1 - 0 !
src/global/dict_ldap.c | 6 3 + 3 - 0 !
2 files changed, 4 insertions(+), 4 deletions(-)

 set default ldap protocol version to 3

conf/master.cf | 56 28 + 28 - 0 !
1 file changed, 28 insertions(+), 28 deletions(-)

 set chroot to default enabled

Makefile.in | 1 1 + 0 - 0 !
rmail/LICENSE | 79 79 + 0 - 0 !
rmail/Makefile.in | 56 56 + 0 - 0 !
rmail/rmail.8 | 49 49 + 0 - 0 !
rmail/rmail.c | 475 475 + 0 - 0 !
5 files changed, 660 insertions(+)

 use sendmail's rmail

html/Makefile.in | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 set lang=c for html documentation build

auxiliary/collate/README | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 debianize collate.pl so we can ship it in the package

makedefs | 5 0 + 5 - 0 !
1 file changed, 5 deletions(-)

 disable ld_library_path check

Conflicts with building with eatmydata (e.g. in salsa-ci).

conf/main.cf | 48 28 + 20 - 0 !
conf/master.cf | 4 2 + 2 - 0 !
2 files changed, 30 insertions(+), 22 deletions(-)

 debian-specific defaults for main.cf and master.cf
Date: Thu, 19 Dec 2024 22:37:11 +0300

conf/post-install | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 run debian-specific configure-instance script from post-install create-missing

conf/postfix-script | 34 34 + 0 - 0 !
src/postfix/postfix.c | 3 3 + 0 - 0 !
src/postmulti/postmulti.c | 3 3 + 0 - 0 !
3 files changed, 40 insertions(+)

 re-run postfix start through systemd
Date: Fri, 13 Dec 2024 21:13:34 +0300

When `postfix start' (or `postmulti start') command is run from command line,
postfix instance is started outside a session manager such as systemd.
This is fine for traditional init-based systems, but systemd has a notion of
a service which it tracks.  Postfix instance started this way line becomes
"orphaned", run within user session which started it, confuses session manager
and other tools which expects mail service to be running.

Systemd exports $INVOCATION_ID when it starts a service.  This variable can
be used as a (weak) indicator that we're running under systemd, so if it
is set, just run `master' process the usual way.  But if it is not set,
and the system is running under systemd (/run/systemd/system is present),
instead of running postfix master process directly, we run the systemd
service which corresponds to this instance.  Which, in turn, should re-run
the same `postfix' command and control will come back to this same place,
where we now start `master' the usual way.

Only the regular `start' command is handled.  All other commands, including
`start-fg', are not modified.

The service being started is either the main/default postfix instance, if
config_directory is /etc/postfix.  Or, the service is assumed to be a path
unit after /etc/postfix-, like config directory being /etc/postfix-foo for
postfix@foo.service, or postfix@foo%2dbar-baz for config directory being
/etc/postfix-foo-bar/baz (see man:systemd-escape for details on the naming).
Other config directories (not prefixed with /etc/postfix-) are not rescheduled
through systemd.

Currently $MAIL_VERBOSE and $MAIL_DEBUG are not passed through to the master
process started through systemd.  It can be implemented if needed.

conf/postfix-script | 11 11 + 0 - 0 !
1 file changed, 11 insertions(+)

 add "debian-systemd-start" subcommand to postfix-script

conf/postfix-script | 69 69 + 0 - 0 !
src/postfix/postfix.c | 23 23 + 0 - 0 !
2 files changed, 92 insertions(+)

 implement "postfix chroot" command

makedefs | 14 7 + 7 - 0 !
src/util/sys_defs.h | 20 11 + 9 - 0 !
2 files changed, 18 insertions(+), 16 deletions(-)

 hurd support v2
Date: Fri, 20 Dec 2024 23:08:37 +0300