Scenario Overview
|
Systems involved |
Mail System |
|
|---|---|---|---|
Variant |
|
Exchange on-premises (or other on-premises) |
Exchange Online |
Filter |
seppmail.cloud |
A |
B |
Supported 3rd party cloud E-mail filter (MIMECAST & Proofpoint) |
C |
||
Other 3rd party E-mail filter (Fortinet, Sophos, Trend Micro, Barracuda) |
D |
- not supported - |
|
Microsoft Defender 365 |
- not supported - |
Z |
|
Supported Scenarios
As of Q1 2024 we differentiate between active and passive support of E-mail flow scenarios in the seppmail.cloud.
Active Support
Scenarios A, B and C
Passive support
Scenarios D and Z
Why passive support:
If your E-mail system interacts with the seppmail.cloud and the E-mail flow is to flow via a 3rd-party component that SEPPmail Secure E-Mail Gateway cannot influence, we offer so-called "passive" support for these scenarios. This mainly concerns on-premises and cloud mail filters with which SEPPmail has no cooperation agreement and therefore no direct access to support and development.
What we offer with passive support:
As part of the onboarding documentation, we describe solution scenarios and suggestions on how to securely and correctly integrate the 3rd party components into the mail flow and prevent mail loops.
We will support analyses of whether mails are received by us or sent by us and arrive at a target host.
What we do not offer with passive support:
SEPPmail will not answer questions about the setup, functionality and possible errors of the 3rd party component.
Scenario A - Exchange on-premises Inline
Scenario B - ExchangeOnline Inline
Scenario C - Supported 3rd party cloud E-mail filter
Scenario D - Other E-mail filter on-premises/cloud
Scenario Z - Exchange Online parallel
