Support For IPv6 Addresses Or Prefixes In MailAllowedServiceAccess, Imap.domainallowed, Etc. (Doc ID 2917664.1)

Last updated on JANUARY 31, 2023

Applies to:

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.