In more complex environments, it might be necessary to route emails which are to be treated exclusively cryptographically via the SEPPmail Secure E-Mail Gateway.

 

In the following scenario, the possibility to decide centrally whether and how emails are to be encrypted/signed during dispatch is no longer possible at the SEPPmail Secure E-Mail Gateway. This control function is taken over by the upstream protection component.
If the individual control of actions on the client is to be maintained, the protection component must be able to interpret the markings implemented via Subject Line Keywords, SEPPmail Microsoft Outlook Add-In, IBM Notes template or Groupwise template.

For incoming emails, the AntiSpam component must be able to reliably detect whether an email is cryptographically treated to route it correctly.

 

Incoming:

 

 

 

 

Outgoing:

To be able to use the Gateway-To-Gateway (Domain) Encryption that is included in the basic licence, but also especially the SEPPmail Managed Domain Service, routing the complete email traffic via SEPPmail Secure E-Mail Gateway is required in this constellation.