[
https://issues.apache.org/jira/browse/JAMES-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038865#comment-17038865
]
Benoit Tellier commented on JAMES-3067:
---------------------------------------
`Have a parameterized number of recursions, doing multiple queries on the
current scheme`
On alias -> finalAddress resolution, we do a recursion with a hard coded number
of recursion step.
Why would we do anything different for the inverse recursion?
After all, we want the list of alias that are actually resolved to the final
user. The number of recursion steps **should be the exact same than standard
than normal RRT resolution** overwize results will diverge.
> The number of queries can easily explode, overloading Cassandra
Please come up with a scenario coming up with an "important number of queries.
We do just that for standard resolution recursion, and I did not hear complains
regarding this.
> Allowed From headers recursion
> ------------------------------
>
> Key: JAMES-3067
> URL: https://issues.apache.org/jira/browse/JAMES-3067
> Project: James Server
> Issue Type: Improvement
> Components: JMAP, SMTPServer
> Affects Versions: 3.5.0
> Reporter: Gautier DI FOLCO
> Assignee: Antoine Duprat
> Priority: Minor
>
> In order to go further than the JAMES-3032 we need to go a recursion-level
> further.
> They are two propositions now:
> * Have a parameterized number of recursions, doing multiple queries on the
> current scheme
> * Have a specific projection maintaining all the connected aliases
> We should discuss it
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
