"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 laterInformation in this document applies to any platform.
Symptoms
On:
Oracle Communications Messaging Server 8.1.0.10.20210504 64bit (built May 4 2021)
and
Oracle Communications Messaging Server 8.1.0.12.20210903 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.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |