-
What is your original issue/pain point you want to solve?
When receiving agent notifications, they always include a link. To prevent easy phishing attempts, it would be useful to easily verify the sender as Zammad. -
Which are one or two concrete situations where this problem hurts the most?
Agent receives a phishing mail in form of an agent notification. He clicks a link in the mail and thinks, he is logged into his Zammad instance. But its a phishing trap instead. -
Why is it not solvable with the Zammad standard?
Because S/MIME (&PGP) can only be used for customer communication, not for agent notifications. -
What is your expectation/what do you want to achieve?
Enable S/MIME-Signing of agent notifications.
Ticket#10111842