The fix could be as easy as
--- a/conf/postfix-tls-script
+++ b/conf/postfix-tls-script
@@ -1039,7 +1039,7 @@ deploy-server-cert)
*) keyfile="${config_directory}/${2}" ;;
esac
But I'm not expert enough to consider all the side effects. Maybe at this point one would better pass "" instead of "enable".
It seems it has been introduced in this form a long time ago at 3.1.0 and was broken since then.
I wonder why nobody ever hit that, maybe it isn't supposed to be used at all?
Since it seems to be broken in the last version as well I wanted to ask you if you'd mind to bug-report that upstream and we could take the fix from there and backport to Ubuntu releases.
But I must admit that I wasn't able to find a proper bug tracker for postfix?!
I guess that means you should report to one of the mailing lists http://www.postfix.org/lists.html and it would be great if you could then get back here and update the bug with the link to the mail archive entry.
That way we can recheck what the outcome there will be and consider backporting it.
The fix could be as easy as postfix- tls-script postfix- tls-script "${config_ directory} /${2}" ;;
--- a/conf/
+++ b/conf/
@@ -1039,7 +1039,7 @@ deploy-server-cert)
*) keyfile=
esac
- deploy_server_cert "${certfile}" "${keyfile}" || exit 1
info_server_ deployed "${certfile}" "${keyfile}" "deploy" | $INFO
+ deploy_server_cert "${certfile}" "${keyfile}" "enable" || exit 1
;;
But I'm not expert enough to consider all the side effects. Maybe at this point one would better pass "" instead of "enable".
It seems it has been introduced in this form a long time ago at 3.1.0 and was broken since then.
I wonder why nobody ever hit that, maybe it isn't supposed to be used at all?
Since it seems to be broken in the last version as well I wanted to ask you if you'd mind to bug-report that upstream and we could take the fix from there and backport to Ubuntu releases.
But I must admit that I wasn't able to find a proper bug tracker for postfix?! www.postfix. org/lists. html and it would be great if you could then get back here and update the bug with the link to the mail archive entry.
I guess that means you should report to one of the mailing lists http://
That way we can recheck what the outcome there will be and consider backporting it.