Initial situation:

The SEPPmail Secure E-Mail Gateway is operated with client capability.

 

Question:

How does the SEPPmail Secure E-Mail Gateway behave during the email communication between the clients?

 

Answer:

For system-related reasons, the standard behaviour on client-capable systems is different during communication between clients is different than during communication with external communication partners.

For instance, if an email to another client on the same SEPPmail Secure E-Mail Gateway is marked as to be encrypted by the sender, it would not make sense to encrypt it only to immediately decrypt it again.

Since the secure communication between the respective email servers of the clients and the shared SEPPmail Secure E-Mail Gateway is a basic requirement in client-capable systems (please also refer to Clients: Securing The Connection Between The SEPPmail Secure E-Mail Gateway And The Email Server), this can be compared to a gateway-to-gateway (domain) encryption. Thus, the emails between the clients should generally be marked as "secure" (please also refer to Incoming e-mails Add this text to message subject after decryption).

This can be realised via the option Consider internally routed mails as encrypted