S/MIME configured but emails not encrypted

Technical assistance
1

Infos:

  • Used Zammad version: 6.5.2
  • Used Zammad installation type: deb package
  • Operating system: Debian
  • Browser + version: any

Expected behavior:

  • We have configured the S/MIME integration, uploaded certs for recipients. When testing that manually, by clicking on the “Email” tab when creating new ticket, the email about new ticket is sent out encrypted ok, as expected. The group settings are set to Sign:no and Encypt: yes. So I would expect that all emails sent out (to those recipients where cert was uploaded) should be sent encrypted by default.

Actual behavior:

  • What we observe, is that emails out are sent still not encrypted, on new tickets created by our customers.

Steps to reproduce the behavior:

  • Create a new ticket, do not use that “Email” tab (the same way as our customers don’t do), and check email that came about the new ticket created. It should be encrypted, but is not.

I’m not sure at all, if this is a big, or if I’m just missing some setting that needs to be set, to make it send all emails out encrypted. Thanks in advance for your help :slight_smile:

2

Hi @paka.

You’re talking about notifications via mail, right? If so, as far as I remember, such notifications are not respecting the S/MIME settings and configuration.

3

But the trigger configuration has explicit settings for encryption and signing - even not sending it if it can’t be encrypted / signed…?

image
image2104×1692 159 KB

4

Yes, for trigger notifications it should be the case, only not for standard notifications.

1 Like