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 "René Cordier (Jira)" <se...@james.apache.org> on 2019/12/05 02:42:00 UTC
[jira] [Closed] (JAMES-2952) Still an infinite loop can be
triggered by failure with Sieve
[ https://issues.apache.org/jira/browse/JAMES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Cordier closed JAMES-2952.
-------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
> Still an infinite loop can be triggered by failure with Sieve
> -------------------------------------------------------------
>
> Key: JAMES-2952
> URL: https://issues.apache.org/jira/browse/JAMES-2952
> Project: James Server
> Issue Type: Bug
> Affects Versions: master, 3.4.0
> Reporter: Pablo Pita Leira
> Priority: Major
> Fix For: 3.5.0
>
> Attachments: 18 Jahre 👑🦁.zip, ID_1fire-37942-1575255756412-5_1_1_1_268.gz, error_log.txt, sieve_rules
>
>
> The infinite loop caused from parsing errors in Sieve still can be triggered in James.
> When processing the problematic message, what got delivered at my inbox and at the sent folder, was the failed message and the new "error" messages with the text [SIEVE ERROR] added to the subject, so recursively.
> A log extract is attached to help find the cause, together with an example of a file stored within ActiveMQ that shows the cause.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org