Recipient Rewrite Table Configuration
Consult recipientrewritetable-template.xml in GIT to get some examples and hints.
JPA Recipient Rewrite Table
The default table for storing James' Recipient Rewrite mappings.
Add a class attribute to recipientrewritetable tag (class="org.apache.james.rrt.jpa.JPARecipientRewriteTable).
- 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.
XML Recipient Rewrite Table
Add a class attribute to recipientrewritetable tag (class="org.apache.james.rrt.xml.XMLRecipientRewriteTable).
- 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.
- mapping
- Example: some@domain=someuser
JDBC Recipient Rewrite Table
Database backed RecipientRewrite table
Add a class attribute and a destinationURL attributed to recipientrewritetable tag (class="org.apache.james.rrt.jdbc.JDBCRecipientRewriteTable" destinationURL="db://maildb/RecipientRewriteTable").
Use these configurations to store the RecipientRewriteTable in a database.
- 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.
- sqlFile
- file://conf/sqlResources.xml
