[
https://issues.apache.org/jira/browse/JAMES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986503#comment-16986503
]
Benoit Tellier commented on JAMES-2952:
---------------------------------------
Hello Pablo,
I will take a look at this today.
At first glance, I would say Sieve mailet should be relying on mailetcontainer
error management in order to allow customization of error management.
Then I would be very curious to actually get the EML of the message causing the
error, as well as the SIEVE script triggering the failure. That would be
invaluable for writing unit/integration tests...
> 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: ID_1fire-37942-1575255756412-5_1_1_1_268.gz,
> error_log.txt
>
>
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
