at the minute we use S/MIME only for signing outgoing emails.
Now, a customer may use our public key to create a ticket with an encrypted email.
When this happens, RT tries to encrypt all subsequent emails like notifying the Requestor and other Watchers defined by a Scrip.
This now usually fails, since we don’t have the respective public keys stored (and probably will have never, our customer base is too large and diverse).
This automatic encryption was introduced by
Is there any way around this ? (Other than patching it out)