[
https://issues.apache.org/jira/browse/JAMES-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3295.
-------------------------------
Fix Version/s: 3.6.0
Resolution: Fixed
> Integration tests : SMTP out - retry back off leveraging MailRepositrories
> and reprocessing
> -------------------------------------------------------------------------------------------
>
> Key: JAMES-3295
> URL: https://issues.apache.org/jira/browse/JAMES-3295
> Project: James Server
> Issue Type: New Feature
> Components: Queue, rabbitmq, Remote Delivery, tests
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.6.0
>
> Attachments: aca6e77b-c720-42a2-b78e-0e74d77aa424.png
>
>
> *Context*
> Distributed James do not support MailQueue delays making it unusable as a MX
> server.
> However given a fixed network of suppliers to work with, delays are not an
> issues, SMTP error just need to be correctly handled.
> retrying without delay could enhance the situation by working around some
> transient remote server errors. It’s better than not retrying at all (or
> doing all the retries without delays).
> Given manual intervention, it is possible to correctly
> *Requirements*
> Such a solution should:
> - Attempt delivery a single time
> - Store transient and permanent failure in different mail repository
> - After a given number of tries, transient failures should be considered
> permanent
> *Definition of done*
> Write potentially failing mailet integration tests demonstrating the above
> proposed RemoteDelivery error handling.
--
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
