Better specifiy and document RecipientRewriteTable --------------------------------------------------
Key: JAMES-1227 URL: https://issues.apache.org/jira/browse/JAMES-1227 Project: JAMES Server Issue Type: Improvement Components: Documentation Reporter: Eric Charles >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" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org