I have an ITSM 14.1 site interested in the following scenario.
Any suggestions on how they might achieve this?
There is a parameter "@NX_EMAIL_ALLOW_UPDATE_ON_INACTIVE" which controls whether Closed tickets may be updated. However, it can't be enabled to prevent updates to Closed tickets, otherwise the CA PAM Web Services updates will stop working.
For issue 00771777.
Here's a thought: given that the site already uses PAM, perhaps they could add a PAM process to monitor the inbox that Maileater is currently configured for, and point Maileater at a new inbox. The PAM process would inspect each incoming email. If the email refers to a Closed ticket, strip out the ticket reference and send the updated email to the new Maileater inbox, where it should cause a new ticket to be raised. Otherwise, forward the email to the new Maileater inbox without alteration, where it will update the ticket.
There may be a touch of the 'Heath Robinson' about this, but I'm sure it would work...
More moving parts than a . . . thing with moving parts. But it actually seems like a nice way of going about it . . . if you can get past added steps to set it up.