If the protection component does not support special routing functions, a double pass of an originally encrypted incoming email through the protection component can be guaranteed without creating a loop by means of header tagging. Here, the SEPPmail Secure E-Mail Gateway assumes the routing.

 

Incoming:

 

 

Here, initially, the protection component forwards the entire incoming email traffic to the SEPPmail Secure E-Mail Gateway. The SEPPmail Secure E-Mail Gateway processes these emails. All unencrypted emails are transferred to the email server after being processed.

Emails decrypted by the SEPPmail Secure E-Mail Gateway are given a special X header and transferred to the protection component again. After being checked for malware by the protection component, the emails are forwarded to the SEPPmail Secure E-Mail Gateway again. Based on the X header set before, the latter recognises that the email was already processed in the first pass and sends it to the email server without any further actions.

 

 

Outgoing:

 

 

Thus, the process for outgoing emails is the same as in the already described scenarioWith Intervening Protection Component.