torsdag 2 maj 2019 kl. 22:41:38 CEST skrev Jeremy Harris via Exim-dev:
> On 01/05/2019 22:54, Magnus Holmgren via Exim-dev wrote:
> > The problem definitely is with primary_hostname getting overwritten with
> > random data after the first message, even though the code sets store_pool
> > =
> >
> > POOL_PERM, as directed by the documentation:
> > /* This needs to be retrieved through expand_string in order
> >
> > not to violate the API. */
> >
> > static uschar *primary_hostname=0;
> > if (!primary_hostname) {
> >
> > store_pool = POOL_PERM;
> > primary_hostname = expand_string("$primary_hostname");
> > store_pool = POOL_MAIN;
> >
> > }
> >
> > Is this a bug in SA-Exim or in Exim?
>
> I don't find that code in the exim source... Is this a local_scan
> function?
That code is from SA-Exim, which implements a local_scan() function. What I
mean is: is there something wrong with this code, or has something been broken
in Exim so that the permanent pool doesn't work?
--
Magnus Holmgren holmgren@???
