features

In Review

Currently, every Mailbox can only upload one S/MIME .p12 or .pfx file.If a User use personas and have similar domains for outgoing mails, they can’t be encoded or signed with S/MIME.<a target="_blank" rel="noopener noreferrer nofollow" href="mailto:username@domain1.com">username@domain1.com</a><a target="_blank" rel="noopener noreferrer nofollow" href="mailto:username@domain2.com">username@domain2.com</a><a target="_blank" rel="noopener noreferrer nofollow" href="mailto:username@domain3.com">username@domain3.com</a>It should be able to add more than one S/MIME certificate, for each outgoing E-Mail account / persona

Currently, every Mailbox can only upload one S/MIME .p12 or .pfx file.If a User use personas and have similar domains for outgoing mails, they can’t be encoded or signed with S/MIME.username@domain1.comusername@domain2.comusername@domain3.comIt should be able to add more than one S/MIME certificate, for each outgoing E-Mail account / persona

Marcin Nolte

Currently, every Mailbox can only upload one S/MIME .p12 or .pfx file.

If a User use personas and have similar domains for outgoing mails, they can’t be encoded or signed with S/MIME.

[username@domain1.com](mailto:username@domain1.com)

[username@domain2.com](mailto:username@domain2.com)

[username@domain3.com](mailto:username@domain3.com)

It should be able to add more than one S/MIME certificate, for each outgoing E-Mail account / persona



S/MIME, ability to upload more then one S/MIME certificate

Subscribe to post