Is it possible to have a separate DLQ for messages which are expire (TTL) and that are rejected (NACK)?
For the expiration it's simple - the queue could have x-message-ttl and x-dead-letter-exchange defined.
Having a DLQ for rejected messages we're trying to achieve retry with back-off. Yes - we could still have a consumer, which instead of rejecting the message (NACK) actually publishes the message to another queue, yet we'd like to keep the consumer as dumb as it goes.
