While you can never be 100% sure that an email message is delivered to a recipient, there are three things you need to do to to ensure delivery of email messages sent through your Mira system. Please contact Mira Live using the chat in you have any questions.
To ensure delivery to external recipients, you need to
1. verify the domain, and
2. configure your DNS-server for the domain(s) you will use as from-email address
To ensure delivery to internal users, you might also need to
3. whitelist Mira as a trusted sender in your internal email server.
For step (1), contact Mira Live and we will send you a verification email that you need to forward to us so we can click the link in the email.
For step (2) and (3), you need to contact your IT-department or supplier that manages your domain (the part of your email address after @). Refer them to this document and they should know what to do.
Ensuring delivery to external recipients
Email messages from Mira systems are sent through the email service provider Mandrill. Mandrill is a transactional email API from Mailchimp. Mailchimp is one of the largest email marketing and newsletter services. Email from Mira, through Mandrill is always sent from a dedicated IP-range, separate from other Mandrill and MailChimp clients. When sending email using a Mira-system, the user can select the From-address for the email. We follow best practices to avoid email sent through Mira to be classified as suspicious. Normally email from Mira have the Sender header set to mnsvc.com, a domain controlled by Mira and that has proper DKIM and SPF-records set. Many email programs will then show in the from field as sent “via” or “on behalf of” mnsvc.com.
To further minimize the risk of email being classified as spam by recipient’s email software, you can add DKIM and SPF records in the DNS for the domain used in the From-header. Most email programs will then no longer show the “via” or “on behalf of” mnsvc.com.
What are DKIM and SPF?
Basically DKIM and SPF are authentication mechanisms that helps Mandrill to send emails on your behalf through your domain.
DKIM is a DNS-based email authentication mechanism that helps Mandrill more effectively send mail on your behalf by allowing receivers to verify that we have permission to send your email. To enable DKIM, create a TXT record for mandrill._domainkey.yourdomain
v=DKIM1; k=rsa; p=
Some DNS providers require that semicolons be escaped. If your provider requires escaping, use this value instead:
v=DKIM1\; k=rsa\; p=
SPF is another DNS-based email authentication mechanism. If you don’t yet have an SPF record, you’ll want to add one for your domain. At a minimum, the value should be the following if you’re only sending mail through Mandrill for that domain:
v=spf1 include:spf.mandrillapp.com ?all
If you already have a TXT record with SPF information, you’ll need to add Mandrill’s servers to that record by adding include:spf.mandrillapp.com in the record (before the last operator, which is usually ?all, ~all, or -all).
Ensuring delivery to internal recipients
In addition to the actions, measures above you might need to whitelist Mira in your internal email system. This is necessary since some email servers do not accept external emails claiming to be from a domain that the server is responsible for to prevent “spoofing” and “phising”. In those cases you need to whitelist or allow “domain impersonation” from Mira.
The exact steps depends of the email server, for Office 365, see Anti-phishing policies – Office 365 | Microsoft Docs. Email messages sent from Mira are sent trough the email server mx.mira.se.