My Oracle Support Banner

The Tr= Field On Ac=Y Should Log The Local IP As Well As Remote IP (Doc ID 2824670.1)

Last updated on DECEMBER 03, 2021

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.


The tr= field on ac=Y should log the local IP address as well as the remote IP address.

Referring to:,-116,310

Smartsend is being used to do round-robin to select the source IP address for outbound connections.
It is working as expected.

But, the log does not indicate which address was chosen for connections which failed.

For example, an attempt to relay a message to, via the external MX, failed.
The reason for the failure was a problem with BGP config for some of the IP addresses. So that is not the issue here.

The log shows 10 ac=Y entries (one for each of the MX records) and then ac=Q.
That all worked as expected. Eventually the message was retried with a valid/working source address and it was relayed.

But the ac=Y log records all have tr= like tr="TCP|||<IP>|25"
They show the IP address of the MX that was attempted to connect to.
But they do not show the source address it tried to connect from.

On successful dequeues, the ac=D record has the transport info in the di= field, eg (TCP|<IP>|26027|<IP>|25).
And the ac=C record has tr="TCP|<IP>|26027|<IP>|25"

But on ac=Y, there is no logging of which source addresses failed.

Is there a logging option that could provide that info?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.