First of all, I would like to congratulate you on your successful installation of Mumara Campaigns+. It’s pretty easy for a mailer to understand what to do next after logging into it for the first time. Moreover we have Basic Steps mentioned in the dashboard that could lead to your first broadcast scheduling. Below you can find out in detail how to proceed with the mandatory steps in order to deploy your very first broadcast.
1) Configure a Primary Domain
In Mumara, you have the opportunity to keep application URL and primary domain name different. Like other applications or even Mumara Classic uses application URL as the main domain name responsible to track emails. In couple of cases (e.g avoiding blacklist, white-labeling etc), you need to keep your application URL out of the tracking loop and yes this is possible in Campaigns+.
Navigate to Settings -> Branding
The first tab you see is for Primary Domain configuration. By default Mumara puts your application URL in the Primary Domain but you always have an option to edit it however it’s not mandatory if you don’t need to have it on a different domain. If you replace the primary domain with another domain name, you’ll need to add an “A Record” in DNS zone for the primary domain and point it to Mumara server IP. Once the “A Record” has been added to domain’s DNS, it means your primary domain is pointing to the Mumara server but you’ll also need add the primary domain to your webserver (e.g apache) on the same physical path as of Mumara so they do proper handshake and propagate. Once everything has been setup, Mumara should pass the result otherwise click on “Recheck” button to verify if its resolving properly.
2) Add a Sending Domain
Sending domain is the one that appears in Mail-From email address when the recipient receives the email. So it’s important to add a sending domain in Mumara and authenticate it by adding a domain-key (if Mumara is responsible to sign your messages). While adding a sending domain, you also have to mention a tracking subdomain that appears in the tracking URLs e.g hyperlinks, tracking pixel etc. To propagate the tracking domain, you’ll need to point/redirect it to the Mumara Primary Domain by cname or .htaccess method.
Authenticate Your Sending Domain
If you want Mumara to sign messages with a Domain Key and you are sure that your MTA/SMTP provider isn’t signing the messages then you can enable domain-key signing in Mumara and it will generate a public key for your sending domain. You have an option to change the domain-key selector, by default Mumara puts “key” as the selector and it appears in email headers. You can simply copy the public domain-key to your sending domain’s DNS as a TXT record.
Tracking domain is a subdomain of your sending domain (e.g if your sending domain is foo.com then tracking domain could be track.foo.com) and is responsible to appear in the tracking links. You can put a redirection using a cname record or htaccess method. For cname redirection, insert a cname entry to your sending domain’s DNS as you see in Mumara. For htaccess method, you need to host the tracking domain somewhere and upload the .htaccess file to the root folder of the tracking domain.
Once your domain key has been inserted and tracking has been configured, click on the “Confirm” button to validate them. If everything is resolving properly, Mumara will give a success message, otherwise you can always fix it and Recheck later.
3) Add Bounce Email/Mailbox
Bounce email acts a return-path and a mandatory field for the message headers. If no bounce email is defined in message headers, the email doesn’t qualify for delivery. To add a bounce email, you’ll need to authenticate it by giving your IMAP/POP connection details. Mumara needs the login details of your bounce mailbox so it can login to read all bounce reports and flag the associated contacts status accordingly within your list.
4) Sending Node
A sending node is carrier that relays your message to the recipient’s mailbox. It can be an SMTP or an ESP (Email Service Provider). We have integrations available with major ESPs i.e Sendgrid, Mailgun, Amazon SES or even PowerMTA (more ESPs are being integrated). If you have an account with any of the listed ESP then you can simply connect it or you can even sign up with them for an instant account. If you are looking to connect an SMTP then add the authentication details and validate the connection.
Make sure you choose the correct/matching Sending Domain and Bounce email here as they will be responsible for qualifying your message.
5) Import Contacts
Once you are done with the above 4 steps, you are all set to send broadcasts. You simply need to create a contact list and import contacts to it before you can schedule a broadcast. Importing process is very simple and it allows you to map the custom fields with your csv file headers. Once the import has been started, you have an option to navigate away from the page as it runs in the background.