title: Dead-letterred messages not getting requeue to original queue after ttl
body: <p>I have planned to delay the processing of messages in queue by following these two links <a href="http://yuserinterface.com/dev/2013/01/08/how-to-schedule-delay-messages-with-rabbitmq-using-a-dead-letter-exchange/" rel="nofollow">link1</a> <a href="http://www.kuntalganguly.com/2015/02/delay-or-schedule-message-delivery-with.html" rel="nofollow">link2</a>. So, as suggested in the link. I have declared the original queue with the <code>x-dead-letter-exchange</code> and <code>x-dead-letter-routing-key</code> args. Which published the messages to the so called <code>dead-letter-queue</code> when message either failed to get processed by consumer or ttl happen or queue length exceed. Now in the <code>dead-letter-queue</code> similar args have been set along with the <code>ttl</code> parameter. Which is suppose to republish the messages to the original queue after <code>ttl</code> exceed. But the problem is it is dropping all the messages. </p>
  
  <p>Moreover, there is a catch here. If i explicitly publish the failed messages from original queue to dead-letter-queue. Then after ttl it republish the messages to the original queue. Why is it so and how do i make it work. So that dead-letter-queue republishes the messages to the original queue instead of dropping. I am using <code>RabbitMQ 3.0.0</code>. </p>
  
  <p>FYI, I have created both the exchanges of <code>direct</code> type along with the routing key</p>