I am using rt the organize a conference program with around 600-700 submission, and need to send acceptance and rejection mails in bulk. I am using both, some hand written python code and the ruby gem roust as plugin to the frab conference planning tool to set Owners, change Subjects and add Correspondence.
Unfortunately, each of those transactions triggers several emails to the Owner, resulting in email storms in the range of 10000s to my event coordinators, that I need to manually filter all mails to the coordinators in postfix. If they happen to also submit to the conference, their acceptance mails will be removed and all notifications to replies to those new correspondences will not reach the coordinators until I remove the postfix filter. Obviously, this is not a good solution.
While in RT’s HTTP interface you can set TxnRecipients to squelch e.g. the Owner, the corresponding parameter is not processed in the REST or REST-2.0 API.
Is there a recommended way to interact with RT to avoid these email storms or would it be possible to make squelching available via one of the REST APIs?