Full Tracking of Header Delete Index When IMMEDIATE_HEADER_MODIFICATION is Set
Last updated on APRIL 25, 2018
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
When the Milter option IMMEDIATE_HEADER_MODIFICATIONS is set, one of the consequences is that the header changes (from DKIM milter) would cause the indexing to change immediately, such that the first delete with index 1 gets the first header, which moves everything down one slot. The second with index 2 now gets the third header, and so on until the indices fail to match anything and they turn into no-ops.
Requesting an option that would make multiple deletes work in any order when IMMEDIATE_HEADER_MODIFICATIONS is set to 1.
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