[
https://issues.apache.org/jira/browse/JAMES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986727#comment-16986727
]
Benoit Tellier commented on JAMES-2952:
---------------------------------------
https://github.com/linagora/james-project/pull/2950 will solve your problem.
The metadata preventing double recomputation was not well positioned.
I believe it would also make sense to have JSIEVE using MIME4J in a lenient
fashion.
Also we should investigate that UTF-8 bug in MIME4J as well...
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
