CONTRIB: MoveTicketToOriginalQueue

RT Users
1

This ScripAction will move a ticket into the queue it was originally
destined for. This could potentially be used to “restart” a ticket’s
journey through a succession of queues; the original requirement was
for an incoming ticket to be able to be placed into a “quarantine”
queue and moved back to where it was originally intended if the
quarantine conditions were met.

This action has an external dependency. You will need to configure
your MTA/MDA to add an “X-RT-Queue: foo” header to the message once
it determines that the message was intended for queue “foo”.
Without this, the scrip cannot (easily and reliably) determine the
original queue (and will refuse to do anything in that case). The
author uses procmail and formail to accomplish this; there are other
ways.

Phil Homewood pdh@snapgear.com 20020626

MoveTicketToOriginalQueue.tar.gz (1.67 KB)

2

This action has an external dependency. You will need to configure
your MTA/MDA to add an “X-RT-Queue: foo” header to the message once
it determines that the message was intended for queue “foo”.

Or you could change rt-mailgate to add the header to the MIME object
before doing the Create(), based on the --queue argument.

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations
3

Bruce Campbell wrote:

This action has an external dependency. You will need to configure
your MTA/MDA to add an “X-RT-Queue: foo” header to the message once
it determines that the message was intended for queue “foo”.

Or you could change rt-mailgate to add the header to the MIME object
before doing the Create(), based on the --queue argument.

No, it’s too late by the time rt-mailgate gets hold of it.
(At least for the spam control/quarantine application.) You
need to set the header to the queue the message was sent to,
not the one it ended up in. :slight_smile: