Sieve Header :mime :anychild :contenttype Doesn't Go Into S/MIME Signed Messages
(Doc ID 2415825.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Using: Messaging Server 184.108.40.206.x
Is the following expected product behavior or is it a bug?
We have the following in a sieve filter on a user:
The reason for the "multipart/signed" is because the "message/rfc822" check does not seem to work on S/MIME signed messages.
It seems as if the :mime :anychild does not look into the structure of the S/MIME signed messages.
Background: This account is where users are supposed to forward **AS ATTACHMENT** false-positives--messages that arrived in their Junk folder when they don't think it was spam.
If it has a message/rfc822 body part, then it probably is a valid message forwarded as an attachment.
If it does not have a message/rfc822 body part, then they probably just used Forward rather than Forward-as-attachment, and therefore will not be valid for attempting to report a false positive, so we want to just discard it.
But we find that if they did forward-as-attachment but they are using S/MIME and signed the message, it still gets discarded.
Thus we think the test for message/rfc822 is not going into the S/MIME signed message structure.
Obviously, if the message is S/MIME encrypted, it would be impossible to look into the structure. But, we are just talking about signed, not encrypted.
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