Major Description
See JAMES-3800
We do encounter a timeout on top of OVH S3 blob store when reading emails.
RabbitMQMailQueue, upon loading exception, does not really handle those exception and let them propagate to the subscriber, here JamesMailSpooler, which handles the exception by just logging it.
THis means the RabbitMQ messages of such emails are never acked nor nacked, stays unacknowledged forever. Unacknowledged messages keeps pile up until there is no space left for legitimate traffic.
At this point the mailQueue consumption halts, James needs to be rebooted which effectively nack those messages.
