Phil Pennock wrote:
> On 2011-06-24 at 15:32 +0000, W B Hacker wrote:
>> Phil Pennock wrote:
>>> On 2011-06-24 at 05:59 +0000, Bruce A. Bergman wrote:
>>> [ headers_remove not working ]
>>>> remote_smtp:
>>>> debug_print = "T: remote_smtp for $local_part@$domain"
>>>> driver = smtp
>>>> headers_remove = "X-FDA:X-Panda:X-Spam-Summary"
>>>
>>> Does it work if you remove the quotes?
>>>
>>> If so, please file a bug (but you'll also have a working config).
>>>
>>> -Phil
>>>
>>
>> Bug?
>>
>> Or documentation change?
>
> Bug. The documentation states that anything specified as being a string
> may be wrapped in quotes, and headers_remove is specified as an expanded
> string.
>
My point.
It appears to be treated in the same manner as, for example, a 'hostlist' or
similar colon-separated critters - most of which do not require quotes.
And - not to put too fine a point on it - but I'm not certain that a header-name
is always (just) a string.
> At this point, I don't know if that's what's happening here; I've been
> very busy this week.
>
Ditto - and for the next two coming.
But - having run production for many years WITHOUT quotes, here's what happens
otherwise:
With double-quotes:
# /usr/local/bin/exim -bd -q55s
2011-06-25 02:00:13 [26013] Exim configuration error in line 1517 of
/etc/exim/configure:
extra characters follow string value for headers_remove
With single-quotes, no error thrown on daemon invocation.
If the first-mile received header of this post is still assigned by tahini, then
my server is still stripping all 'received' headers on the outbound, and Exim
accepts EITHER single-quotes or no-quotes.
CAVEAT: I DO use a space either side of the colon.
Bill
I'm sending this WITH quotes to see if, as I suspect, the code is clever enough
to sort it.
