[jira] [Commented] (JAMES-3700) Dead letter policy for the Pulsar MailQueue

["Ha Anh Vu (Jira)" <se...@james.apache.org>]

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

Ha Anh Vu commented on JAMES-3700:
----------------------------------

Yeah I may have overthought a little bit..

 

Anyway, I sent a draft PR: https://github.com/apache/james-project/pull/952

 

Can you take a look and see if I'm going the right way or not?

> Dead letter policy for the Pulsar MailQueue
> -------------------------------------------
>
>                 Key: JAMES-3700
>                 URL: https://issues.apache.org/jira/browse/JAMES-3700
>             Project: James Server
>          Issue Type: Sub-task
>          Components: pulsar, Queue
>    Affects Versions: master
>            Reporter: Benoit Tellier
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Currently the Pulsar MailQueue do not come up with a dead-letter policy.
> A bad JSON payload halts the processing. 
> This makes the Pulsar MailQeue brittle:
>   - The ability to inject a single message with a bad payload can cause an entire James cluster to come to a halt.
>  - Could be seen as an attack vector
>  - But also any changes to the underlying JSON schema for payloads is susceptible to cause major downtime.
> We should define a deadletter policy:
>  - Given a number of failures delivery of the message would be abandonned
>  - And moved to a dead-letter topic for later audit (prevent data loss)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org