Incorrect Original Recipient Can Result When Using Sieve Redirect
(Doc ID 2773207.1)
Last updated on OCTOBER 30, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
An incorrect original recipient can be the result when using sieve redirect.
When using sieve redirect, an incorrect ORCPT can be added in the message header and also logged in the original destination address (od) field in the logs.
As an example, an email sent from usertest0 to usertest12 and usertest5 is received by userA due to a sieve redirect.
Where mailSieveRuleSource is set only for usertest12:
then the original recipient is recorded correctly in the log and also in the message header.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!