On 22/09/2020 01:41, Jim Fenton via Exim-users wrote:
> I’m not sure whether
> this would be considered a bug or just a misconfiguration, but I’m happy
> to create a bug report if appropriate.
Yes please; any crash that can be induced by a particular config is
a bug, even if the config is not
On 18 Sep 2020, at 17:09, Jeremy Harris via Exim-users wrote:
On 17/09/2020 23:30, Jim Fenton via Exim-users wrote:
So instead I have tried putting into my mail_spool transport:
headers_add = ${authresults {$primary_hostname}}
but I'm not seeing the header field in locally-delivered messages
On 19/09/2020 05:08, Jim Fenton via Exim-users wrote:
> On 9/18/20 5:09 PM, Jeremy Harris via Exim-users wrote:
> Related question: when a router does a headers_add, does it only do that
> if that router accepts?
The documentation does say, in the obvious place:
"a list of text headers [...]
On 9/18/20 5:09 PM, Jeremy Harris via Exim-users wrote:
> On 17/09/2020 23:30, Jim Fenton via Exim-users wrote:
>> So instead I have tried putting into my mail_spool transport:
>>
>> headers_add = ${authresults {$primary_hostname}}
>>
>> but I'm not seeing the header field in locally-delivered
On 17/09/2020 23:30, Jim Fenton via Exim-users wrote:
> So instead I have tried putting into my mail_spool transport:
>
> headers_add = ${authresults {$primary_hostname}}
>
> but I'm not seeing the header field in locally-delivered messages (yes,
> I am using mail_spool local delivery). Is this
Hi,
I'd like to add the Authentication-Results: header field only to
messages that are being delivered locally; it doesn't make sense for me
to attach it to outgoing messages.
I started out by putting in the acl_check_data ACL:
warn
add_header = :at_start:${authresults
