Allow different lmtp_host in postfix_lmtp file
Currently, lmtp_host
configuration parameter is being used both to bind LMTP runner (code) and for postfix_lmtp
file generation (code).
It causes an issue when the binding hostname is different from that one, which is used externally. For example, in Kubernetes setup LMTP runner should be bound to pod's hostname while postfix_lmtp
file should contain linked service name instead. (It can be also seen as a load balancer in front of mailman-core
which provides access to LMTP listener.)
This is a blocker for Mailman 3 migration to Kubernetes, to resolve, lmtp_host_external
parameter might be added to overwrite lmtp_host
for postfix_lmtp
file.