However, this configuration was not required on stretch. On buster, when the dovecot-lmtp gets the email for delivery, it considers it for the alias (eg log dovecot: auth: Debug: master in: USER#0112#011ada.lovelace@[…]) whereas on stretch it considers it for the already resolved user (eg ada@). I cannot see in the logs before dovecot-lmtp takes over where it would be different. The postfix ldap-aliases seem to do the work and resolve the alias ok.
The check-utf8-email.yml in tests is sending to an alias.
If you think this shouldn't be needed and can find a better fix in the integration between postfix and dovecot, it would be welcome.
This change makes the aliases working on buster.
However, this configuration was not required on stretch. On buster, when the dovecot-lmtp gets the email for delivery, it considers it for the alias (eg log
dovecot: auth: Debug: master in: USER#0112#011ada.lovelace@[…]
) whereas on stretch it considers it for the already resolved user (egada@
). I cannot see in the logs before dovecot-lmtp takes over where it would be different. The postfix ldap-aliases seem to do the work and resolve the alias ok.The
check-utf8-email.yml
in tests is sending to an alias.If you think this shouldn't be needed and can find a better fix in the integration between postfix and dovecot, it would be welcome.