Re: [exim] using environment ${env {}} for helo_data

Top Page
Delete this message
Reply to this message
Author: Heiko Schlittermann
Date:  
To: exim-users
Subject: Re: [exim] using environment ${env {}} for helo_data
Frank Heydlauf via Exim-users <exim-users@???> (Mi 29 Jul 2020 22:12:13 CEST):
> > >      ...
> > >      # helo_data = ${env{EXIM_HELONAME}{$value}{heloname-undefined}}
> > >      helo_data = ${env {EXIM_HELONAME}}
> > >      ...
> > >      # for debugging only:
> > >      headers_add = "X-HOSTNAME: ${env {EXIM_HOSTNAME}}"
> > >      headers_add = "X-EH: ${env {EH}}"
> > >      headers_add = "X-EXIM_HELONAME: ${env {EXIM_HELONAME}}"

>
> After a several tests I guess ${env {}} is just not set/expanded
> in the transports section.
> However, I could not find anything about that in the dokumentation.


That is very unlikely. Either expansion is applied or not. But from what
I understand (whithout explicitly checking now) from the code is, that
we have an "expand" function, and there is no list of items to be
expanded or not expanded. But… I might be wrong.

Can you post the smallest working config that you use to reproduce the
behaviour?

    Best regards from Dresden/Germany
    Viele Grüße aus Dresden
    Heiko Schlittermann
--
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --------------- key ID: F69376CE -