Note: The instruction below only applies to the scenarios A, C and D. For these, the mail system connectivity must be configured inside the mail system and in the seppmail.cloud portal.

All Exchange Online scenarios (B, Z) are automatically prepared. If you use Exchange Online as your mail system, all settings in the seppmail.cloud portal are pre-set and integration works with our PowerShell module, see chapter SEPPmail365cloud PowerShell Module.

Mail directions

From an Internet perspective we distinguish between inbound traffic (coming from the Internet) and outbound traffic.

Inbound E-mails flow to the recipient of the customer's organization, outbound traffic is flowing from the customer's users to external recipients.

Changes in the seppmail.cloud portal for scenarios A, C and D

The seppmail.cloud portal has two sections for the mail configuration, called "eingehend (inbound)" and "ausgehend (outbound)".

Scenario A - Inline with on-premises mail system

Scenario B and Z

Settings in the seppmail.cloud portal are automatically deployed correctly for all Exchange Online scenarios. All you need to do is to follow the guidelines to enable the mail flow with our Exchange Online PowerShell module, which is documented in chapter SEPPmail365cloud PowerShell Module.

Scenario C and D  - parallel with 3rd party cloud or on-premises mail filter

In general, this scenario means that E-mails are routed through the seppmail.cloud in parallel for cryptographic processing and then routed back to the origin system.

For scenario C with the MIMECAST Cloud we have a special setup documentation which can be found in the SEPPmail Secure E-Mail Gateway documentation.