[JAMES-1227] Better specifiy and document RecipientRewriteTable

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Documentation
• Assignee: Unassigned
• Reporter: Eric Charles
• Created: 19/Apr/11 11:08
• Updated: 30/Aug/24 07:09

Description

From discussion on mailing list (http://markmail.org/message/abyqit3iiahaqque), we need to better specify and document the Recipient Rewrite Table functionality.

Quoted from Stefano mail:
-------------------------------------

Are the mapping rules applied until the first match or instead are all
applied to the last rule?
Are the mapping rules applied recursively until you find matches or
instead only once?

e.g, I add this mappings / rewrites:
a => b
b => c
b => a
d => f
e => d
f => g

Who receives messages destinated to a? b, c+a or does it loops?
Who receives messages to d? f or g?
Who receives messages to e? d or g?

These are the questions I make when I see e rewrite engine, I would
never expect the answers to the above questions to be: "if X is local
then Y, otherwise if it is remote Z, if instead it is local but non
existing then K"

Issue Links

• is part of: JAMES-3193 Update Developer Guide
• is related to: JAMES-3330 Clarify Recipient Rewrite Table Configuration (recipientrewritetable.xml)