Can we consider setting OriginalDestination property on the ActiveMQMessage when sending it to the DLQ in Camel?

That would be useful for tools like Hawt.io or FMC. For example FMC relies on the OriginalDestination to provide "retry" functionality. Currently Camel doesn't set OriginalDestination, so we can't retry the delivery of the AMQ messages from Camel DLQ.