Recipient Rewrite Table Configuration
Consult recipientrewritetable.xml in GIT to get some examples and hints.
Mapping types
James allow using various mapping types for better expressing the intent of your address rewritting logic:
- Domain mapping: Rewrites the domain of mail addresses. Use it for technical purposes, user will not
be allowed to use the source in their FROM address headers. Domain mappings can be managed via the CLI and
added via WebAdmin
- Domain aliases: Rewrites the domain of mail addresses. Express the idea that both domain can be used
inter-changeably. User will be allowed to use the source in their FROM address headers. Domain aliases can
be managed via WebAdmin
- Forwards: Replaces the source address by another one. Vehicles the intent of forwarding incoming mails
to other users. Listing the forward source in the forward destinations keeps a local copy. User will not be
allowed to use the source in their FROM address headers. Forward can
be managed via WebAdmin
- Groups: Replaces the source address by another one. Vehicles the intent of a group registration: group
address will be swapped by group member addresses (Feature poor mailing list). User will not be
allowed to use the source in their FROM address headers. Groups can
be managed via WebAdmin
- Aliases: Replaces the source address by another one. Represents user owned mail address, with which
he can interact as if it was his main mail address. User will be allowed to use the source in their FROM
address headers. Aliases can be managed via WebAdmin
- Address mappings: Replaces the source address by another one. Use for technical purposes, this mapping type do
not hold specific intent. Prefer using one of the above mapping types... User will not be allowed to use the source
in their FROM address headers. Address mappings can be managed via the CLI or via
WebAdmin
- Regex mappings: Applies the regex on the supplied address. User will not be allowed to use the source
in their FROM address headers. Regex mappings can be managed via the CLI or via
WebAdmin
- Error: Throws an error upon processing. User will not be allowed to use the source
in their FROM address headers. Errors can be managed via the CLI
JPA Recipient Rewrite Table
The default table for storing James' Recipient Rewrite mappings.
Using Spring, you should add a class attribute to recipientrewritetable tag (class="org.apache.james.rrt.jpa.JPARecipientRewriteTable). It has no effect with Guice wiring.
- recursiveMapping
- If set recursiveMapping false only the first mapping will get processed - Default true.
- mappingLimit
- By setting the mappingLimit you can specify how much mapping will get processed before a bounce will send. This avoid infinity loops. Default 10.
