It appears to be running afterwards. I've renamed the scripts, prepending 100 to the reassignment scrip and 110 to the autoreply scrip, so that they are listed in the proper order, and confirmed in the apache log that the requestors are changed before the autoreply scrip is run. Unless there is an order-of-execution nuance that escapes me, it appears that the requestor is replaced first. I could be missing something, though, as there is another scrip that, according to the log, is executing between those two, despite not being listed between them.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Glenn Sieb Sent: Friday, January 10, 2014 11:42 AM To: [email protected] Subject: Re: [rt-users] Autoreply to new requestors -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/10/14, 12:17 PM, Abraham Liebsch wrote: > I have a scrip that, when a ticket is created by email by under > certain conditions, will delete the email sender as the requestor and > replace it with a different requestor (in order to permit creating > tickets on behalf of others). I have confirmed this scrip works > properly, and that this scrip executes prior to the default scrip > which autoreplies to ticket creators. Yet, the autoreply is being sent > to the email sender and not to the new requestor. Does anyone have a > suggestion to ensure the autoreply is sent to the newly-set requestor > and not the email sender? Is the Autoreply scrip before or after the replace-the-requestor scrip? Best, - --Glenn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLQMNkACgkQf5MxTDXTimFVegCfUqnGPBGfytg9wTziYNGZft4o 6pYAmgKS82cMFgwjFnn46iDubwRZ7fIw =76uH -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME cryptographic signature
