When inbound mail arrives at a Scanner, Symantec Messaging Gateway verifies that the message is addressed to a valid local domain before accepting it to the appropriate message queue.
You must define any domain for which you want Symantec Messaging Gateway to accept inbound email as a local domain. Symantec Messaging Gateway only accepts inbound email that is addressed to local domains. However, a domain from which you send email can be a local domain or a non-local domain.
Defining more than one domain lets you assign different routing and delivery options to each domain, including TLS encryption for secure delivery, for local or non-local domains. By configuring TLS encryption options for non-local domains, you can secure connections for delivery by external servers.
You can also enable DKIM signing for a local or non-local domain, so that each message sent from that domain will include a DKIM signature that enables DKIM authentication by the receiving MTA.
You can also add non-local domains. You specify non-local domains primarily to route outbound email over established connections to external servers for non-local delivery. You can also define delivery options for non-local domains.
Several features of Symantec Messaging Gateway make use of domain designations.
You can add or edit domains to:
Create different email acceptance settings for each domain.
Typically, a domain is the part of the recipient's email address that follows the @ sign. For example, anywhere.com is the domain for firstname.lastname@example.org. Domains can include subdomains. For example, somewhere.anywhere.com is a subdomain of anywhere.com. Alternatively, you can specify a single email address as a domain.
If you want to include all subdomains with a domain, enter a period before the domain. For example, if you want to include all subdomains in example.com, enter .example.com. However, entering a period before the domain omits the domain itself. For example, to accept email that is addressed to example.com and all subdomains of example.com, you must specify both example.com and .example.com.
If you want to include only certain subdomains, you must specify each subdomain separately. For example, you must specify both elsewhere.anywhere.com and somewhere.anywhere.com as separate domains to accept email that is addressed to either subdomain but not overthere.anywhere.com.
A domain can be a fully qualified domain name (FQDN), subdomain, or RFC5321-compliant email address. These levels of granularity allow you maximum control over what addresses are acceptable and how email that is addressed to them are routed.
Imported Document ID: HOWTO92436
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe