Hello list,
Is there an example of a script to prevent duplicate emails? We often have
users adding an owner as a CC, or adding someone as a CC and a one-time CC,
or for other reasons adding someone to a ticket multiple times. I've
accepted that user training won't solve this completely, so is ther
On Wed, Dec 07, 2016 at 11:46:44AM -0500, Alex Hall wrote:
> Hello list,
> Is there an example of a script to prevent duplicate emails? We often have
> users adding an owner as a CC, or adding someone as a CC and a one-time CC,
> or for other reasons adding someone to a ticket multiple times. I've
Hi all,
In my last email, I asked about duplicate messages being sent out and was
told to check the RT workflow and enabled scripts. In doing so, I realized
I don't quite get how different scripts fire or are ignored.
For instance, we have a global script that notifies owner and CCs on ticket
corr
On Dec 7, 2016, at 1:17 PM, Alex Hall
mailto:ah...@autodist.com>> wrote:
I guess that's it for now. I'd like a way to watch the different scripts do
their thing for a single transaction, and I need to better understand how the
different scripts decide when to fire and when to stay quiet. Thanks
I'm trying to setup rt 4.4.1 to send s/mime signed email. After some
fussing around and figuring out that openssl couldn't handle the full
chain of certificates in the pem file it generated itself, I got RT to
send signed messages, however Thunderbird complains that they got
modified after signing
A couple of other questions:
1. I built a pem CA repository using:
http://anduin.linuxfromscratch.org/BLFS/other/make-ca.sh-20161126
http://anduin.linuxfromscratch.org/BLFS/other/certdata.txt
then pointed CAPath at the resulting directory, but it doesn't trust
my incoming signed mail
