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 "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/11/27 14:39:00 UTC
[jira] [Closed] (JAMES-3861) EmailDelivery push is used too much
[ https://issues.apache.org/jira/browse/JAMES-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3861.
---------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> EmailDelivery push is used too much
> -----------------------------------
>
> Key: JAMES-3861
> URL: https://issues.apache.org/jira/browse/JAMES-3861
> Project: James Server
> Issue Type: Improvement
> Components: JMAP
> Reporter: Tran Hong Quan
> Assignee: Antoine Duprat
> Priority: Major
> Fix For: 3.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As of today, we push an EmailDelivery for each "added" event.
> Yet, added event is used for copies, move, saving draft, sending email... In addition to received new emails.
> We should revisit the APIs of `MessageManager::append` in order to allow passing a bit more context. This context would need to be carried other in the event system.
> # Definition of Done
> JMAP integration test showing that EmailDelivery` state change is reserved to receiving email...
> # API proposal
> Add a `isDelivery` field to the append command, defaulting to false.
> Add a isDelivery field to the `Added` event, defaulting to false.
> Ensure LocalDelivery sets the isDelivery to true.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org