Transport Rules are generated during the onboarding process and are created by the PowerShell Module.
To change them (order, enable/disable, settings in 200), use the Exchange Online Admin Portal.
Sections on this page:
Inline Mode
Rule Number: 060
Direction: Inbound
Customizing: No
Explanation: Sets a ruleversion header so that the seppmail.cloud can identify outdated transport rule settings.
Rule Number: 200
Direction: Inbound
Customizing: No
Explanation: Marks E-mails for seppmail.cloud internal operations. Do not modify this rule, as all traffic will be send to seppmail.cloud anyway in inline mode.
Parallel Mode
Rule Number: 060
Direction: Inbound
Customizing: No
Explanation: Sets a ruleversion header so that the seppmail.cloud can identify outdated transport rule settings.
Rule Number: 100
Direction: Inbound
Customizing: Not recommended
Explanation: Signed and/or encrypted E-Mails are send to seppmail.cloud for decryption/signature check. You could change this to route all E-mails to seppmail.cloud. This will have unwanted side-effects for special E-mail types like OOF, Sharepoint Mails and so on. Handle with care!
Rule Number: 110
Direction: Inbound
Customizing: No
Explanation: Remove and clean fake-subject-tags.
Rule Number: 200
Direction: Outbound
Customizing: Yes
Explanation: seppmail.cloud processes e-mails cryptographically. You could add conditions like special groups or users and limit the users which will use seppmail.cloud.
Rule Number: 300, 400, 500, 600, 700
Direction: Outbound
Customizing: No
Explanation: seppmail.cloud cleans any remaining X-header information to obfuscate cryptographic handling to the internet and any external recipient.
