How to set up a Delivery Server?

Step 1: Go to “Delivery Servers” under the Servers section.

Step 2: Click on “Create new server”.

Step 3: A dialog box will pop up, asking you to choose your delivery server. If you don’t have any you can register for one just by clicking the right arrow.

Let’s say you have a Mailgun server. Select the Mailgun Web API.

Step 4: Now fill out the following details related to your server

  • Name: The name of this server to make a distinction if having multiple servers with the same hostname.
  • Domain name: Server Verified domain name.
  • API Key: Your API Key
  • From Email: The default email address used in the FROM header when nothing is specified
  • From name: The default name used in the FROM header, together with the FROM email when nothing is specified
  • Probability: When having multiple servers from where you send, the probability helps to choose one server more than another. This is useful if you are using servers with various quota limits. A lower probability means a lower sending rate using this server.
  • Hourly Quota: In case there are limits that apply for sending with this server, you can set an hourly quota for it and it will only send in one hour as many emails as you set here. Set it to 0 in order to not apply any hourly limit.
  • Daily Quota: In case there are limits that apply for sending with this server, you can set a daily quota for it and it will only send in one day as many emails as you set here. Set it to 0 in order to not apply any daily limit.
  • Monthly Quota: In case there are limits that apply for sending with this server, you can set a monthly quota for it and it will only send in one monthly as many emails as you set here. Set it to 0 in order to not apply any monthly limit.
  • Pause after send: The number of microseconds to pause after an email is sent. A microsecond is one-millionth of a second, so to pause for two seconds you would enter: 2000000
  • Tracking Domain: The domain that will be used for tracking purposes, must be a DNS CNAME of the master domain.
  • Use for: For which type of sending can this server be used for
  • Force from: When to force the FROM address. Please note that if you set this option to Never and you send from an unverified domain, all your emails will fail delivery. It is best to leave this option as is unless you really know what you are doing.
  • Reply-To Email: The default email address used in the Reply-To header when nothing is specified
  • Force Reply-To: When to force the Reply-To email address
  • API region: The Geo-region of your API

Domain Policies: If your delivery server cannot send emails to certain domains, or it can only send to a small list of domains, you can add domain policies to reflect this. If you want to send emails only to yahoo.com but deny for any other domain, you will need a allow policy for the domain yahoo.com and a deny policy on domain * If you want to send to all domains except yahoo, then a deny policy on yahoo domain is enough. If you want a policy for all yahoo emails, including yahoo.co.uk, yahoo.com.br, etc you can simply enter “yahoo” as a policy domain. The sign * acts as a policy wildcard matching any domain. A domain of domain*.com or *domain.com has no effect.

Additional Header: If your delivery server needs extra headers in order to make the delivery, you can add them here. If a header is not in the correct format or if it is part of the restricted headers, it will not be added. Use this with caution and only if you know what you are doing, wrong headers can make your email delivery fail. Following dynamic tags will be parsed depending on context: [CAMPAIGN_UID], [SUBSCRIBER_UID], [SUBSCRIBER_EMAIL]

Step 5: Once you have filled out and saved your details. You will receive an email to activate your domain server (In the email you provided above). Your domain server will be inactive till you activate it with the link provided in your email.

Get Answers to All Your Questions You Might Have

We will answer any questions you may have about our products.