Re: [Exim] FW: Problem expanding added headers (v3.35)

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Philip Hazel
Datum:  
To: John R. Shearer
CC: exim-users
Betreff: Re: [Exim] FW: Problem expanding added headers (v3.35)
On Mon, 23 Jun 2003, John R. Shearer wrote:

> If I am reading this right, then expand.c isn't expanding added headers
> because they're not in the link list it is checking. This would explain the
> behavior I'm seeing.


I ignored your post because it referred to Exim 3, and my brain has now
more or less expunged any memory that I had, since Exim 4 has been out
for well over a year (and I've been working on it for about 2 years
now).

> Is this expected behavior, or am I doing something wrong?


Yes, it is expected, and it is the same in Exim 4, where the manual
contains the following in the section on $header_xxx insertions:

   Only header lines that are common to all copies of a message are visible to
   this mechanism. These are the original header lines that are received with
   the message, and any that are added by an ACL "warn" statement or by a      |
   system filter. Header lines that are added to a particular copy of a
   message by a router or transport are not accessible.


--
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book