A quick follow up to state that
https://github.com/linagora/james-project/pull/4110 implemented that ;-)
Cheers,
Benoit
Le 03/12/2020 à 09:08, btell...@linagora.com (OpenPaaS) a écrit :
> Nice to see we are on the same wave length!
>
> Regarding the upgrade path, I'm in favor of
Le 04/12/2020 à 03:21, Jean Helou a écrit :
> Hello fellow jamers !
>
> The Jenkinsfile in the PR works, up until the test suite fails, the tests
> failures are from seemingly "unstable" tests that fail because of timing
> issues. Benoit fixed the first one in
>
Hi,
I'm currently trying to increase overall efficiency of the Distributed
James server.
As such, I'm pocking around for improvement areas and found a huge topic
around LWT.
My conclusions so far are that we should keep LWT and SERIAL consistency
level out of the most common use cases.
I know
Nice to see we are on the same wave length!
Regarding the upgrade path, I'm in favor of requiring an empty mailQueue.
Rationals: if there is any sort of retro-compatibility, then an attacker
controlling ie the JMS solution would still be able to control the
deserialized payload (and trigger all