Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 9.0.0


  1. Pick the FROM domain
    Which domain will you be using to send emails with MailUp? Your top-level domain (i.e. the apex domain as discussed above) or a subdomain (e.g. In the first scenario, the FROM EMAIL would be something like, whereas in the second it would be something like The decision should be based on whether you have access and can modify the DNS records of that domain. Check with the person in your organization that has access to your domain management system to find the answer. In the examples below we are assuming that the sending domain corresponds to the apex domain ( If you cannot modify the DNS records of your apex domain, then you will need to set up a subdomain (eg and refer to that one (in place of in the steps outlined below.
  2. Verify your FROM EMAIL
    Now that you have picked the FROM domain, create a FROM EMAIL under that domain, and verify it in your MailUp account. To prevent abuse, MailUp requires that the FROM EMAIL is verified before it can be used. Verification is very simple: MailUp will send a verification message to the provided FROM EMAIL address, and you will need to click the link contained in the message. You can verify the FROM EMAIL when you configure a List in your MailUp account, when you set up a new mailing or when you add a new From email in Deliverability checkup page.
  3. Configure the SPF record for the sending domain
    Adding SPF authentication is easy. Here is what you need to do:

    • Contact your Web hosting company, domain registrar, or network administrator that manages this domain
    • Tell them that you need to make a change to the DNS (Domain Name System) records
    • If you are not already publishing an SPF record, ask them to add the following TXT record:  

    v=spf1 ~all 

    • If you already have an SPF record in place (e.g.: you have a TXT record starting with v=spf1) then you should only add the "" before the final "all" keyword

    Example: v=spf1 ~all ~all 

    • Wait 24-48 hours: it takes a bit of time to changes to the DNS to propagate around the Internet
    • Run the SPF test in Deliverability checkup to confirm that the SPF record has been successfully updated.

  4. Enable DKIM authentication
     Adding DKIM authentication is easy. Here is what you need to do:
    • Contact your Web hosting company, domain registrar, or network administrator that manages this domain
    • Tell them that you need to make a change to the DNS (Domain Name System) records
    • Ask them to create the following two CNAMEs (replace "" with your domain)
    • ... and point it to
    • ... and point it to
    • If a CNAME cannot be created, you may also establish DKIM authentication by adding the following TXT records to the DNS settings. Please contact us for additional details
    • Wait 24-48 hours: it takes a bit of time to changes to propagate around the Internet
    • Run the DKIM test in Deliverability checkup to confirm that the CNAMEs have been successfully updated.

  5. Configure a Web interface domain (optional)
    If you wish to use a custom Web interface domain (see the Glossary above for a definition), create a C-NAME in your domain management system (e.g. and point
    For more information, please see MailUp account settings. Please note that this configuration is available only for PRO and ENTERPRISE clients. 

  6. Configure a custom Envelope Sender (optional)
    Using a custom Envelope Sender (see the Glossary above for details) you can to "align" it with the FROM EMAIL address, which allows for more advanced sender configurations, as mentioned above. This address can be any email account of your choice under the same domain as the one used for the FROM EMAIL (e.g. if the FROM EMAIL is the Envelope Sender could be In order for the MailUp system to be able to process bounces, it will need to access sent to that address. There are two options:

    1. You may provide us with POP3 access to that mailbox (port 110, PLAIN no TLS or SSL)

    2. You may forward messages received by that mailbox to a specific email address that we will provide

  7. PTR of SMTP servers (For dedicated IPs):
    If your email streams will be delivered through dedicated SMTP servers, each one of them should have a PTR aligned with the base host domain. Example: A A

    Each PTR should have the same SPF / Sender ID records as the sending domain: TXT v=spf1 ~all TXT spf2.0/pra ~all


  8. Enable DMARC
    Since DMARC is built upon SPF and DKIM all the previous steps are required before enabling DMARC.

    The proper TXT record ( should be added to the DNS settings for your sending domain.
    It can change depending on what you want your DMARC policy to be.

    A simple DMARC record is the following: v=DMARC1; p=quarantine; pct=100;;
    * v is the version, DMARC1 is the only version available at the moment.
    * p is the policy. Allowed values are *none* (take no action, just collect data and send reports) *quarantine* (treat with suspicion unqualified mail) *reject* (block any unqualified mail for the domain)
    * pct is the percentage of non-aligned messages that should be rejected (from 1 to 100 where 100 means all the messages)
    * rua: Send aggregate reports to this address (should be closely monitored)
    * ruf: Send forensic (detailed) reports to this address.

    Note that the email addresses that receive the aggregate and detailed reports (“rua” and “ruf”) can be on any domain, not necessarily the domain used for the authentication, for reporting purposes only.

    We strongly suggest ramping up DMARC use slowly by using the p=none policy at first. Monitor your traffic and look for anomalies in the reports (eg.: messages that are not yet being signed)
    Then, once you have verified that all legitimate messages are correctly being authenticated, move to "quarantine."
    Review the results again (look also in your spam folder) and when you're absolutely sure all of your messages are signed, change the policy setting to "reject" to make full use of DMARC.

    You can also leverage the pct tag to sample your DMARC deployment. If you want to be extremely conservative, after moving to the quarantine policy, you may start with pct=1 and then move to 10, 25, 50, 100...