prosgarz35 commented on PR #3205:
URL: https://github.com/apache/james-project/pull/3205#issuecomment-5825217271
Thank you for this crucial insight and real-world perspective, @chibenwa!
The scenario where the source delete actually succeeded on the database
side while the reactive driver timed out (or experienced internal queue
saturation) makes total sense: a compensating delete on the destination would
result in
total, irrecoverable message loss.
"Too much data is better than data loss" is definitely the right guiding
principle here — having a failed move gracefully degrade into a copy is vastly
safer and completely manageable for IMAP clients/users.
Closing this PR accordingly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
