How to Use the Catchall Feature
(Doc ID 1458790.1)
Last updated on JANUARY 31, 2022
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
There are times when you may want mail addressed to a user which is not defined in your LDAP to be accepted instead of rejected and for various reasons it does not make sense to simply define the address either as a new user or by adding it as a mailAlternateAddress or mailEquivalentAddress on an existing user.
You may want various forms of similar addresses -- for example <anything>_support@<DOMAIN>.com -- to go to an individual, and you want to allow for variations or typos in those addresses.
The Catchall features
This can be accomplished with the catchall features of the MTA. There are a few ways to accomplish this.
Also note the subaddressing alternative
You might consider instead of using addresses like <anything>_support@<DOMAIN>.com, use addresses like support+<anything>@<DOMAIN>.com. This is called a "subaddress".
For example, if mail is sent to email@example.com, the MTA will attempt to delivery it to a folder called "somefolder" instead of the the user's INBOX. If the folder does not exist or does not have appropriate permissions, it will instead go to the inbox. Nothing needs to be configured in the MTA to allow this form of subaddressing.
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
|The Catchall features|
|Also note the subaddressing alternative|
|The mailDomainCatchallAddress attribute on the domain|
|The mailDomainCatchallMapping attribute on the domain|
|Use of a partial address in a mailEquivalentAddress attribute on a user|