On 03/07/2017 02:19 PM, Christian Kivalo wrote:
Am 7. März 2017 20:00:55 MEZ schrieb Robert Moskowitz <r...@htt-consult.com>:
After a bit of reflection, I may have asked the wrong question. Perhaps
a better question is does the substitution take place on processing the
option?
What about testing the assumption? Build the configuration and try to make a
tls secured connection, it either works or you will see the error in your logs.
I am days away for a working server. Well, maybe I can test on
another... hmmm.
I plod along testing each build step out, going back to checkpoints and
moving forward again. Now it is the Postfix configs.
Just changed my configuration to use $myhostname variable for the cert name
filename and that works very well. Thanks for the idea.
Thanks for trying it out! I am working on minimizing the places where I
have to customize my howto, so that I can better remember what I did
years ago. Plus share it with others.
And this would apply also to smtpd_tls_cert_file.
thanks
On 03/07/2017 01:59 PM, Robert Moskowitz wrote:
Is there a way to get the following:
postconf -e 'smtpd_tls_key_file =
/etc/pki/tls/private/$myhostname.key'
To work and substitute the value for $myhostname?
I am building a new server and writing up my scripts and I am trying
to adhere to the lessons I learned here some 2+ years ago. And trying
to be better than I was then...
Thank you.
