received-log-format verified
Shape of an intake line
in the configuration this is a line
received-log-format: [{$date}]{if $json.message_id} {$json.message_id} {/if}<{$json.envelope}> <{$json.recipient}> [{$json.connection.remote_ip}] [{$json.connection.local_ip}]Template for intake lines, addressing the incoming message JSON directly and guarding the message id with a conditional.
Values
- Values
literal text with {$json.path} substitutions and {if …}{/if} conditionals- Default
[{$date}]{if $json.message_id} {$json.message_id} {/if}<{$json.envelope}> <{$json.recipient}> [{$json.connection.remote_ip}] [{$json.connection.local_ip}] · taken from the build- applying
restart required- where it can be set
in the config file · with a startup flag · as an environment variable
In detail
Shipped as [{$date}]{if $json.message_id} {$json.message_id} {/if}<{$json.envelope}> <{$json.recipient}> [{$json.connection.remote_ip}] [{$json.connection.local_ip}] — note $json.connection.*, which reaches into the nested connection object. Everything the incoming message carries, including the results of SPF, DKIM and DMARC checks when they are enabled, is addressable the same way.