Comment 1 for bug 613424

Now when clicking on "View mailin quarantine" in the admin UI, each entry in the quarantine will have 'Requeue' and 'Delete' buttons. Additionally there are global 'Requeue all' and 'Delete all' buttons at the top of the screen. When a message is requeued is removed from the quarantine and placed back in the regular queue for processing. The intent is for this operation to be performed *after* steps have been taken to correct whatever problem caused the message to be quarantined. Requeue should be used preferentially over delete. When a message is deleted it is simply removed from postoffice entirely--no further processing will be performed. This operation may be useful in the case where a message is obviously junk mail which would have been bounced by the system anyway, and a system administrator merely wants to clear the error status for the quarantine. Steps should still be taken, however, to ascertain the cause of the message being quarantined and fix the problem so messages (even junk mail) do not end up in the quarantine in the future.

A strategy for testing on staging would be to place some messages in quarantine artificially. Some steps to do that:

1) Turn off mailin for one of the staging instances.

2) Send email messages to an address bound for that instance.

3) Log in to the staging server as postmaster.

4) $ cd /home/postmaster/postoffice

5) $ bin/po_debug

6) >>> print '\n'.join(root.keys())

  (Will show list of queues available.)

7) >>> q = root['<instance>-staging']

  (Make sure you get the *staging* queue for the instance you are testing.)

8) >>> q.quarantine(q.pop_next(), 'Some error message.')

  (This will place a single message in the quarantine. This step can be repeated for as many messages as are in the queue.)

9) >>> import transaction

10) >>> transaction.commit()

Now that you have messages in the quarantine, you can test. Wash, rinse and repeat.