"tl=" Not Logged From Sieve Transactionlog Action When Message Is Rejected
(Doc ID 2963629.1)
Last updated on JULY 25, 2023
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.20.20220923 64bit (built Sep 23 2022)
"tl=" is not logged from the sieve transactionlog action when a message is rejected.
role.channel:process_milters.sourcefilter = file:///<path>/config/checkHeader
$ cat checkHeader
It just never logs the tl= when the checkHeader script rejects the message.
Changes
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! |