Control: tag -1 + pending After a lot more thoughts and experiments, this is the setup so far.
1. `postfix start' uses `systemctl postfix start' internally when run from command line. 2. postmulti configuration is not used in systemd at all. The default postfix.service is started the normal way, and only this one. 3. Additional instances are started by creating postfix@INST.service, where $MAIL_CONFIG is /etc/postfix-INST - ie, by adding "/etc/postfix-" prefix to the systemd instance name, ignoring multi_instance_name entirely (so we don't search for the right config_directory). The multi_instance_name is completely ignored by systemd. 4. Only instances with "/etc/postfix-" prefix in config_directory are managed under systemd. There's no provision for other naming scheme. 5. No non-default instances are started automatically, each non-default instance has to be enabled (systemctl enable postfix@INST.service) explicitly. 6. Readme file and NEWS has been updated. Also, postinst scripts checks for multi-instance configuration and warns the user if now-unsupported config is found. Hopefully I haven't missed something. Please speak up now if you have any comments and suggestions. Current WIP of the next release is in "mjt" branch on salsa, being rebased all the time. The commits about this setup are these (current hashes, will change after a rebase; the names shouldn't change hopefully): 9d519a69 add NEWS and README about changes wrt multiple instances 06a7d4b3 postinst: detect if multi-instance was in use and warn the user 9a96de3b re-run-startup-throug-systemd.patch: direct regular startup to systemd 5c4b686e switch from postfix@-.service to postfix.service: breaking change (#1088862 #928187) Thanks, /mjt
