...
Whilst technically compatible, we don’t yet have an export/import feature, logged as:
JEMH-7545 / JEMHC-2380
Message Filters
JEMH Server/DC had this section, in cloud it doesn’t exist as a section in its own right, the configuration has largely been implemented as settings within the Profile, mostly at the Profile level, for example:
Catchemail Address Filter doesn't exist, you can specify Profile > Catchemail Addresses, and set a Non-catch Email Action.
Status Notification Filter doesn’t exist as there is no Status Notification feature in cloud (nor in current JEMH DC versions)
X-Jira-Fingerprint Filter doesn’t exist as mail doesn’t come from Jira it comes from JEMHC, we do detect inbound mail sent by JEMHC as Precedence:bulk
Whitelisting/Blacklisting Filter is implicit by the global configuration existing, so can’t be opted out of
User Signup Filter doesn't exist as the User signup/configuration is not implemented in JEMHC
X-Spam-Flag Filter has been included through a more general feature, JEMHC > Profile > Drop Messages With Headers (Messages with a header matching a provided key-value pair will be silently dropped. Values can be regular expressions).
Notifications
JEMH Server/DC notifications are not compatible with JEMHC.
...
These are a functional redo. Cloud apps have an app-permission that needs to be granted in the Project Permission scheme to Use Ad hoc notifications.
System Notifications
See JEMHC > Licensing > System Notifications, there you can setup recipients who will be notified of system availability and usage.
...