My Oracle Support Banner

"tl=" Fields Are Not Logged From Sieve Transactionlog Action When Message Is Rejected (Doc ID 2897379.1)

Last updated on SEPTEMBER 26, 2022

Applies to:

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



Oracle Communications Messaging Server 64bit (built May 4 2021)
Oracle Communications Messaging Server 64bit (built Sep 3 2021)

The "tl=" fields are not logged from the sieve transactionlog action when a message is rejected.

With the following configuration:

The transactionlog action succeeds in adding the expected tl= field to the Enqueue/dequeue (en) log entry except for the last condition.

If it hits the "104" case, the message is rejected, as expected, but the en log entry with ac=R does not contain the tl= field.


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

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

In this Document

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