Dňa 16. apríla 2023 20:28:30 UTC používateľ Lance Lovette via Exim-users
napísal:
>tls_certificate =
>/etc/letsencrypt/live/${readfile{/etc/mailname}{}}/fullchain.pem
I lost context, but content of /etc/mailname is in ETC_MAILNAME
macro on debian systems.
regards
--
Slavko
https://www.slavi
"Those options that undergo string expansion before use are marked with †."
Thanks! It's always the fine print that gets you :)
After further investigation (thanks -d+expand!), I must retract my earlier
statement about my readfile assignment not causing any issues. It was :)
╭considering: $prima
On 16/04/2023 19:35, Lance Lovette via Exim-users wrote:
That would be helpful. Can you point me to a reference?
https://exim.org/exim-html-current/doc/html/spec_html/ch-main_configuration.html#SECTalomo
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-use
> I'm not seeing why the default of the "uname" result... is not sufficient
in that case.
Long story short, changing uname to be something other than the container
name will cause ripple effects in other places.
My ultimate goal with setting 'primary_hostname' is to control the host
name exposed
On 16/04/2023 17:52, Lance Lovette wrote:
My goal is to have a single configuration file that can run across
different environments (dev/stage/live.)
I'm not seeing why the default of the "uname" result, used
if you don't set this option, is not sufficient in that case.
FWIW, the readfile ass
My goal is to have a single configuration file that can run across
different environments (dev/stage/live.)
I was really hoping Exim had an evaluate-once assignment operator like
the Makefile walrus (:=).
No problem, I'll come up with a different solution - an include with
macros or just a simple
I'd like my TLS certificate paths to be dynamic and based on
primary_hostname. They're currently defined as such:
tls_privatekey = /etc/letsencrypt/live/${primary_hostname}/privkey.pem
This works fine *if* primary_hostname is defined with a string literal.
primary_hostname = smtp.mydomai
On 15/04/2023 19:36, Lance Lovette via Exim-users wrote:
But I need primary_hostname to be dynamic, say read from a file.
primary_hostname = ${readfile{/etc/mailname}{}}
You can't do that; the primary_hostname option does not
expand it's argument.
Could you explain your need further? Wh