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 2018/06/19 08:19:00 UTC

[jira] [Commented] (JAMES-2414) SpamAssassin HAM SPAM reports should be asynchronous

    [ https://issues.apache.org/jira/browse/JAMES-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516781#comment-16516781 ] 

Tellier Benoit commented on JAMES-2414:
---------------------------------------

Asynchronous execution lead to bugs:
 - StoreMessageManager might unalocate resources before the listener could be executed, resulting in errors. 

Solution had been to copy the message.

While doing this, we also removed the "attachment capability constraint".

https://github.com/linagora/james-project/pull/1484 contributed this.

> SpamAssassin HAM SPAM reports should be asynchronous
> ----------------------------------------------------
>
>                 Key: JAMES-2414
>                 URL: https://issues.apache.org/jira/browse/JAMES-2414
>             Project: James Server
>          Issue Type: Improvement
>            Reporter: Tellier Benoit
>            Priority: Major
>
> SpamAssassin do have a significant impact on James performance (LocalDelivery mailet and JMAP moves have several second delays).
> I would propose to perform asynchronously the spam/ham report operations.
> We should have a MailboxListener configuration parameter to perform this synchronously in tests.



--
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