All settings in IMSS or IMSVA will be migrated to Cloud Email Gateway
Protection completely or partially except those listed in Data that will not be migrated. Among the settings that are partially migrated, some are modified to adapt to Cloud Email Gateway
Protection due to the feature differences between IMSS or
IMSVA and Cloud Email Gateway
Protection. Therefore, you need to confirm or fix
these settings according to the on-screen instructions after migration.
The following table lists some examples of the settings that will be partially migrated
and
describes the feature differences.
NoteFor details about all the settings that are completely or partially migrated, see
the
data migration report downloaded from the Cloud Email Gateway
Protection
administrator console when the migration completes.
|
Navigation in IMSS or IMSVA
|
Source Settings
|
Navigation in Cloud Email Gateway Protection |
Destination Settings
|
Feature Differences
|
||
|
The following settings on the Step 1: Select Recipients and
Senders screen:
|
The following submenus under the Inbound Protection and
Outbound Protection menus:
|
The following settings in the Senders section of the
Recipients and Senders tab:
|
LDAP users in IMSS or MISVA are migrated as static email addresses in Cloud Email Gateway
Protection.
|
||
Condition match settings on the Step 2: Select Scanning
Conditions screen
|
|
Condition match settings in the Advanced section of the Scanning Criteria tab |
Only content filtering supports all condition matched
(AND).
|
|||
True file type settings in the Attachment section of the
Step 2: Select Scanning Conditions screen
|
|
True file type settings in the Advanced section of the
Scanning Criteria tab
|
Cloud Email Gateway
Protection does not support MSI, PNG, 7-Zip, or
Microsoft Windows shortcuts.
|
|||
Global DKIM Enforcement rule
|
|
Settings in the Default (for unspecified domains) policy
(including the action and Enforced Peers)
|
Cloud Email Gateway
Protection uses both the header sender address
and envelope sender address instead of only the header sender address for matching
the list of enforced peers.
|
|||
|
The settings of the following approved lists:
|
|
The settings of the following approved lists:
|
Cloud Email Gateway
Protection uses the envelope sender address
instead of the header sender address for matching the list of ignored peers.
|
||
|
Name and address settings of an address group
|
|
Name and address settings of an address group
|
Cloud Email Gateway
Protection supports wildcard domains (for
example, *@*.example.com) in hybrid address groups, and does not support wildcard
domains in internal address groups.
If an address group is used as senders (or sender exceptions) in outbound policies
or recipients (or recipient exceptions) in inbound policies and the group contains
email addresses from unmanaged domains, Cloud Email Gateway
Protection will create a copy of the address group, delete those email addresses from the
copy, and suffix the copy name with " - internal".
|
||
|
Match settings of a keyword or expression
|
|
Match settings of a keyword or expression
|
None
|
||
|
Variables list in the settings of a policy notification
|
|
Variables list in the settings of a policy notification
|
Cloud Email Gateway
Protection does not support the following
variables:
|
||
|
The following settings of an approved list:
|
|
IP address settings in the IP addresses section
|
Cloud Email Gateway
Protection does not support the following
settings:
|
||
|
The following settings of a blocked list:
|
|
IP address settings in the IP addresses section
|
Cloud Email Gateway
Protection does not support the following
settings:
|
||
|
DMARC settings
|
|
DMARC settings
|
Cloud Email Gateway
Protection uses both the header sender address
and envelope sender address instead of only the header sender address for matching
the list of enforced peers.
|
||
|
Advanced settings of DKIM signatures
|
|
Advanced settings of DKIM signatures
|
Cloud Email Gateway
Protection does not support exempt domains.
|