LPool Not Aware Of Case Sensitivity
(Doc ID 2616627.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
It appears that the LPool (API) code is not aware of case sensitivity.
A personal whitelist feature exists which uses the mgrpAllowedBroadcaster attribute.
The mgrpAllowedBroadcaster attribute is defined as CES (case exact), which means if a sender is defined as being whitelisted by mgrpAllowedBroadcaster=userA@domain.com
and that sender sends from UserA@domain.com, the whitelist lookup does not find it, because with CES userA is not equal to UserA.
An idea to solve that problem was to have the sieve_extlists mapping table do the lookup twice:
once as before with:
* and once with the sender address shifted to lower case:
However, the Lpool code does not do the second search. It uses the cached result of the first search.
Excerpt from the tcp_local_slave log that illustrates the issue:
Looking at the above:
Line 837: Entry #1 matched.
Line 849: See it is going to do the lookup with UserA
Line 850: LDAP lookup failed (expected)
Line 852: Entry #2 matched. This is the one that has $\ and $_ around the address it is supposed to try find in LDAP.
Line 853: you can see it is now using userA
Line 854: "Cached URL resolution"
Due to this issue, a second search is not being performed so it never sees the sender's address as lower case.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!