You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2019/03/26 04:45:00 UTC
[jira] [Resolved] (JAMES-2682) Infinite loop can be triggered upon
Sieve failure
[ https://issues.apache.org/jira/browse/JAMES-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit resolved JAMES-2682.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.4.0
The pull request solved the issue
> Infinite loop can be triggered upon Sieve failure
> -------------------------------------------------
>
> Key: JAMES-2682
> URL: https://issues.apache.org/jira/browse/JAMES-2682
> Project: James Server
> Issue Type: Bug
> Components: Mailet Contributions
> Affects Versions: master, 3.3.0
> Reporter: Tellier Benoit
> Priority: Major
> Fix For: 3.4.0
>
>
> As pointed out by [~pleira], failing sieve processing can generate an mail infinite loop.
> SieveExecutor::handleFailure sends a mail to the user, that is also SIEVE processed (and thus fails) creating a loop.
> To prevent this loop, we should avoid Sieve processing on Sieve error notification emails.
> In Sieve executor, position a `"SieveNotification" -> true` mail attribute in `SieveExecutor::handleFailure`. In SieveExecutor::execute check this mail attribute and if present and true, do not perform the execution. You will write a unit test in SieveIntegrationTest - Emails with this attribute should not be processed.
> If you have any issue don't hesitate to reach us in https://gitter.im/apache/james-project
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org