FORWARD Mapping For SMTP Breaks Fileinto Sieve Rules
Last updated on SEPTEMBER 01, 2017
Applies to:Oracle Communications Messaging Server - Version 7.0.4 and later
Information in this document applies to any platform.
Oracle Communications Messaging Server 7u4-27.04(18.104.22.168.3) 64bit (built Mar 7 2013)
The FORWARD mapping that we set up for SMTP servers breaks sieve fileinto actions.
Here's an example of a sieve rule that was broken:
if header :contains "X-Suspected-Spam" "true"
1. Set USE_FORWARD_DATABASE=64 in option.dat.
2. Add a "fileinto" sieve rule to a test user.
3. Add a FORWARD mapping similar to:
4. Send a message to the test user that matches the conditions for your sieve rule. Observe what is logged and where the message is actually filed.
Here's a message that should have been filed into junk:
However, it was delivered to the inbox instead.
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 hundreds of Community platforms