Support For IPv6 Addresses Or Prefixes In MailAllowedServiceAccess, Imap.domainallowed, Etc.
(Doc ID 2917664.1)
Last updated on JANUARY 31, 2023
Applies to:
Oracle Communications Messaging Server - Version 8.1.0 and laterInformation in this document applies to any platform.
Goal
We currently use mailAllowedServiceAccess values like:
mailAllowedServiceAccess: +ALL:n.n.n.n/255.n.n.n,10.n.n.n/255.n.n.n,100.n.n.n/255.n.n.n
What would IPv6 addresses or prefixes look like in that?
Currently our back-ends all have only IPv4. So controls on connections from front-ends to back-ends still only require IPv4 syntax.
Unauthenticated access to the MTA via IPv6 from clients to front-ends is also not a problem, because that would be handled in MTA mapping tables, which support IPv6.
Authenticated access to the MTA is a problem because that also obeys mailAllowedServiceAccess.
Most of our users currently have something like this:
mailallowedserviceaccess: +ALL:n.n.n.n/255.n.n.n,10.n.n.n/255.n.n.n,100.n.n.n/255.n.n.n
Authentication via IMAP over IPv6 to the MMP fails with:
This is mostly about IMAP access via the MMP.
Solution
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
Goal |
Solution |
References |