Hello Jeremy,
Thank you for the reply.
You have a few great points in there.
1) Putting items directly in the queue was not my first choice and I'm
certainly open to doing it in a more sustainable way. Can you think of another
way? Is there a way to do a "local" delivery that I could setup to bypass all
the other stuff and just try to deliver a message I pass it or put it directly
in the queue?
2) Thank you for your feedback on how to do a custom acl - I've put in the
following custom acl for now.
acl_log_headers:
warn log_message = X-CMS-IssueID $h_X-CMS-IssueID
condition = ${if def:h_X-CMS-IssueID: {yes}{no}}
warn log_message = X-CMS-ContactID $h_X-CMS-ContactID
condition = ${if def:h_X-CMS-ContactID: {yes}{no}}
warn log_message = X-CMS-SubscriberID $h_X-CMS-SubscriberID
condition = ${if def:h_X-CMS-SubscriberID: {yes}{no}}
3) Unfortunately I get an error when I add event_action to my remote_smtp
transport.
remote_smtp:
driver = smtp
interface = ${lookup{$primary_hostname}lsearch{/etc/mailips}}
helo_data = $primary_hostname
event_action = ${acl {acl_log_headers}}
I get an error stating option "event_action" unknown.
Is there another build I need or something? I'm running the standard package
for centos 6.8 exim version 4.84.
Thanks everyone for your help.
Dan Liles
-----Original Message-----
From: Exim-users [mailto:[email protected]]
On Behalf Of Jeremy Harris
Sent: Tuesday, December 13, 2016 5:52 PM
To: [email protected]
Subject: Re: [exim] logging custom headers on send out
On 12/12/16 17:20, Dan Liles wrote:
> I'm thinking I can link this to the msg:delivery event. The main thing I'm
> having trouble with is finding examples.
In your transport put something like:
event_action = ${acl {log_deliv}}
and define an acl like:
log_deliv:
warn condition = ${if eq {tcp:connect}{$event_name}}
condition = ${if def:host}
logwrite = $host: DNSSEC - ${if def:lookup_dnssec_authenticated \
{\"$lookup_dnssec_authenticated\"}{unknown}}
accept
obviously ajusted as needed for your case.
> 1) Our technology inserts the items in the /var/spool/input directory ( sub
> directory ). It's the same process on both the cpanel server and the centos
> server. The cpanel server does seem to log stuff properly though.
This is fragile.
I hope you realise that Exim, and the developers of Exim, consider the spool to
be owned by Exim.
File names, locations, formats and contents are liable to change from release
to release.
If it breaks, you get to keep both parts.
--
Cheers,
Jeremy
--
## 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/
--
## 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/
