Creating and verifying mail sender configuration with a domain

Create a mail sender configuration by using a domain and verify it. After verification, set the mail sender configuration to active for MaaS360® Mail communication.

About this task

After you create a mail sender configuration by using a domain, you must verify the domain. After verification, you can send emails from any subdomain or email address of the verified domain without individually verifying each email. Creating a mail sender configuration by using a domain eliminates the need to create and verify individual email addresses unless you want to apply custom configurations to a specific email address.

For example, if you create and verify a mail sender configuration by using the music.com domain, you do not need to create separate mail sender configurations for subdomains like a.music.com and a.b.music.com, or for email addresses like user@music.com and user@a.music.com.

Creating a mail sender configuration with a domain

Create a mail sender configuration with a domain to brand the sender mail address and display name. The sender mail address is the email address that sends MaaS360 email messages.

Before you begin

You must have an access to the DNS provider of the domain.

Procedure

  1. From the IBM® MaaS360 Portal Home page, select Setup > Branding.
  2. On the Brand My Portal page, click Advanced branding.
  3. On the Advanced Branding page, expand Email sender configuration.
  4. Click Create new.
  5. On the Create new mail sender configuration page, select Domain in the Sender type section.
    Note:
    • Domain is the recommended mail sender configuration type and is selected by default.
    • To comply with Domain-based Message Authentication, Reporting & Conformance (DMARC), you must configure either a custom MAIL FROM domain, or DomainKeys Identified Mail (DKIM), or both.
  6. In the Domain configuration section, provide the following details.
    1. Enter the domain name in the Primary domain field.
    2. To configure a custom MAIL FROM domain, select the Use custom MAIL FROM domain checkbox and enter the subdomain that you want to use in the MAIL FROM domain field.
      Note: The MAIL FROM domain must be a subdomain of the parent domain. You cannot use the subdomain name that you send or receive emails as a value for the MAIL FROM domain field.
    3. Enter the Mail address and the Display name that you want to use to send MaaS360 email messages.
    4. Click Next.
  7. To configure DKIM, provide the following details in the DKIM configuration section.
    Note: As part of the domain verification process, you must configure DKIM to validate email authenticity.
    1. Select an option for the Configure DKIM signing key length based on the signing key length for DKIM algorithm supported by the DNS server.
      Note: By default, RSA_2048 is selected and is the recommended signing key length for DKIM algorithm to enhance security.
    2. Select the DKIM Signatures checkbox to validate messages and prevent forgery or alteration during transit of an email.
      Note: By default, the DKIM Signatures checkbox is selected.
    3. Click Create.
      A new mail sender configuration is created and configured with a custom MAIL FROM domain and DKIM, and a summary report is displayed in a slide-over window. The summary report provides information about next actions.
      Note: The advanced branding can contain a maximum of five mail sender configurations in addition to the existing default mail sender configuration provided by MaaS360.

What to do next

Verifying a mail sender configuration with a domain
After you create a mail sender configuration with a domain and configure a custom MAIL FROM domain and DKIM, you must complete the verification process to verify your domain.
Note: To verify the ownership of a domain, you must have access to the DNS settings of the domain to add the necessary records.
To complete the verification process and to show the updates, download and publish the DNS records to the DNS provider of the domain. For more information on downloading DNS records, see Downloading DNS records.
Note: The DNS provider might take up to 72 hours to detect the DNS records.