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/08 04:30:00 UTC
[jira] [Commented] (JSIEVE-110) improve handling of problems when
processing messages through JSieve
[ https://issues.apache.org/jira/browse/JSIEVE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787520#comment-16787520 ]
Tellier Benoit commented on JSIEVE-110:
---------------------------------------
Hi,
It looks like a beautiful infinite loop upon error handling for Sieve...
Maybe the simplest way to defend against this would be to *not execute* Sieve against SIEVE-ERROR messages.
We may do so using a mail attribute to bypass Sieve mailet evaluation (say skipSieveEvaluation = true)
Do you want to provide such a fix? We may guide you via gitter.
Cheers,
Benoit TELLIER
> improve handling of problems when processing messages through JSieve
> --------------------------------------------------------------------
>
> Key: JSIEVE-110
> URL: https://issues.apache.org/jira/browse/JSIEVE-110
> Project: James jSieve
> Issue Type: Bug
> Components: JSieve (Main), Mailet
> Reporter: Pablo Pita Leira
> Priority: Major
>
> The handling of problems when processing messages through JSieve is not robust.
> The case I like to describe is caused when a ParseException is produced while processing a message (for example, being hit by MIME4J-253),
> org.apache.james.mime4j.field.address.ParseException: Encountered "\r" at line 1, column 42.
> Was expecting one of:
> ":" ...
> "<" ...
> <DOTATOM> ...
> "\"" ...
> <DOTATOM> ...
> "\"" ...
> The current logic produces a new message being preceded in the subject with [SIEVE ERROR]. This message enters the JSieve processing chain again and again is processed, and another message now with the subject starting with [SIEVE ERROR][SIEVE ERROR] is produced. And so goes on and on several hundred of times. That fills the mailbox and it is not desired.
> An example of a message that relates to MIME4J-253 is
> [https://www.mail-archive.com/server-dev@james.apache.org/msg59652.html]
> And the header that is causing the exception:
> From: =?utf-8?Q?R=C3=A9mi_Kowalski_=28JIRA=29?=
> <se...@james.apache.org>
>
>
--
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