[ 
https://issues.apache.org/jira/browse/JAMES-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benoit Tellier closed JAMES-3444.
---------------------------------
    Fix Version/s: 3.6.0
       Resolution: Fixed

https://github.com/linagora/james-project/pull/4035

> JMAP mailetcontainer validations: allow alternative configurations
> ------------------------------------------------------------------
>
>                 Key: JAMES-3444
>                 URL: https://issues.apache.org/jira/browse/JAMES-3444
>             Project: James Server
>          Issue Type: Improvement
>          Components: configuration, JMAP
>            Reporter: Benoit Tellier
>            Assignee: Antoine Duprat
>            Priority: Major
>             Fix For: 3.6.0
>
>
> # Why?
> Today the position of JMAP mailets is hardcoded in transport processor, and 
> the matcher is hardcoded to RecipientIsLocal, duplicated.
> Given a Distributed James server, backed by a LDAP for identity,
> Each RecipientIsLocal mailet will trigger a call to the LDAP for each 
> recipient.
> Standard good practices we apply at linagora is to extract all the local 
> delivery logic in its own processor in order not to duplicate this matcher.
> However given current checks, we can not move JMAP and Vacation mailets in 
> our local delivery pipeline.
> # Expected outcome
> I expect to be able to optimize the usage of those matchers by grouping the 
> delivery logic into a dedicated processor, including "JMAP mailets".
> # How
> For servers powering JMAP, change the default configuration to extract a 
> "local-delivery" processor out of "transport" processor.
> The JMAP checks should then accept these mailets in a "local-delivery" 
> processor, but keep accepting them in "transport" processor for backward 
> compatibility
> # Definition of done
> The default mailetcontainer.xml for JMAP backed servers should have a single 
> RecipientIsLocal matcher.



--
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

Reply via email to