james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-520) Create a RemoteDelivery service
Date Tue, 14 Mar 2017 02:30:41 GMT

    [ https://issues.apache.org/jira/browse/JAMES-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923443#comment-15923443

Tellier Benoit commented on JAMES-520:

Switching processors d'ont involve anymore passing by the mailqueue.

Maybe we should re-introduce a mailet for that.

However, RemoteDelivery have been refatored and is extracted as a separate service.

> Create a RemoteDelivery service
> -------------------------------
>                 Key: JAMES-520
>                 URL: https://issues.apache.org/jira/browse/JAMES-520
>             Project: James Server
>          Issue Type: Sub-task
>          Components: Remote Delivery
>            Reporter: Stefano Bagnara
>            Assignee: Norman Maurer
>             Fix For: 3.0.0
> I already did it.
> A top level service, like the SpoolManager that handle the remote delivering of messages
stored in its own spool.
> You can configure multiple SpoolManagers and the remotedelivery mailet could be replaced
by a simple "ToRepository".
> Working on the integration with the SpoolManager refactorings this could be improved
to have much more control on the delivery workflow (bounce, delay and more) and much better
support for customisation.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message