My Oracle Support Banner

Definition Of "invalid" Folder Names And Setting store.allowbadmailbox (Doc ID 2350682.1)

Last updated on MARCH 06, 2023

Applies to:

Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.


Using:  Oracle Communications Messaging Server 64bit (built Dec 22 2017)

Regarding the following previous KM document: 

Rehostuser / Imsrestore Fails With Error: Invalid Mailbox Name (Doc ID 2341647.1)

A bug was logged at the customer site for the mail client and the response was:

"…technically not required per rfc terminology - SHOULD does not equal MUST/REQUIRED/SHALL…"

Can more explanation be provided on why Oracle thinks these folder names are invalid and should be rejected?

We want the client and the server to be standards compliant, but if this isn't a "MUST", maybe we could just set store.allowbadmailbox and forget about it?

As an example, the following symptom / error can be avoided by using the Allowbadmailbox Option....

Default behavior:
. create "Test Ge&AwE-rard/test"
. NO [CANNOT] IMAP mailbox name contains invalid or denormalized encoding

Set the restricted 'Allowbadmailbox' store option:

# /opt/sun/comms/messaging64/sbin/msconfig set -rest store.allowbadmailbox 1

# /opt/sun/comms/messaging64/sbin/stop-msg
# /opt/sun/comms/messaging64/sbin/start-msg

Testing the behavior after setting the restricted 'Allowbadmailbox' store option:

. create "Test Ge&AwE-rard/test"
. OK Completed



To view full details, 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 a vibrant support community of peers and Oracle experts.