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
(yes,
I am using mail_spool local delivery). Is this the wrong approach?
It's not one I'd considered. My assumption was that since
one does authentication in the various ways as Exim accepts
the message, that was when the results would be recorded.
Obviously I wasn't thinking hard enough.
I think it will mostly, but not quite all, work.
Bits of the ARC info, for example, I think will not.
Basically, all the items that are made
available as exim variables will be ok (because they get
passed along with the message even in spool files).
Other info will not.
That’s what happened; the DKIM authentication results were not
included when the header field was added in this manner.
You could, in acl, plonk the header string into a variable
which this one transport then used to add it as a header.
This must be the way to go (haven’t done this yet). But when I put the
above line into the appropriate router config, an Exam process crashed
with a segmentation violation when I locally sent a message to myself
(the message was queued, and this happened on each queue run).
Apparently those variables aren’t always populated. 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.
-Jim
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
