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/
