@PAUL FALLOWS Unfortunately, I believe there is no way to change this as this is handled by the binding directly with no options exposed to configure this.
Instead, you could either do one of the following:
- Handle Poison Messages Explicitly
This requires you catching errors and sending messages to the poison queue due to invalid content or whatever your scenario demands.
This, however, does not handle the case for where messages are sent to the poison queue for cases where you do not catch errors on.
- Forward Messages from Poison Queue
This approach would be to have a separate function that monitors the poison queue and re-queues messages as appropriate to another queue with all the properties set.