Brandle uses an email service called Mandrill to send emails from the Brandle Presence Manager. We do this because of the volume of mail the Brandle System processes (e.g. when sending campaigns and the monitoring and patrol emails) would cause problems. A large mail processor like Mandrill or SendGrid is designed for this purpose.
So, when sending these mass emails, we construct the emails (e.g. for monitoring) and an email template (for campaigns) and hand them off to Mandrill via their API. Mandrill then processes the emails sending them to the recipients. For monitoring emails, they come from team@brandle.net and we have validated our sending domain, so Mandrill can deliver those emails with authority as brandle.net. For campaigns, we send the mail as one of the customers (e.g. someone@your company.com), so unless the sending domain is validated Mandrill can not send the message authoritatively as someone@your company.com.
Mandrill has the best link describing the process here: https://mandrill.zendesk.com/hc/en-us/articles/360038803434.
But we have also listed the specifics for each type of email that come from the system:
1. Monitoring emails that are sent automatically to Administrators of your account. These come from team@brandle.net in the morning if the nightly monitoring detected something like newly discovered Pops or Criteria conditions.
For this scenario, you will need to have your IT department whitelist brandle.net and mandrillapp.com so these emails (and our direct communication to you) can pass your firewall.
2. Emails you or a team member sends to people from the system. Emails can be sent from a POP Note, a Contact Note, a Task, Campaigns, and POP Issues in the GRC module. The same service also allows Brandle to receive emails back from your Contacts (as a reply to emails you've sent) so a response can be added to the Note. Ensuring that the records are set correctly is critical to your communication process with your contacts.
For this scenario, your IT department will need to add Mandrill to your company domain SPF record. This will ensure the email communications are working effectively and are sent to your contacts using your email address ( xxx@yourcompany.com). Your IT department will need to make a couple of minor changes to your DNS settings so the mail service knows we have permission to send email on your behalf.
Here are the steps needed to include Mandrill in your domain SPF record.
If you don't yet have an SPF record, 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).
Add a new TXT record with the name mandrill._domainkey.yourdomain.com (just replace yourdomain.com with the domain you're setting up).
The value for the record should be one of the options listed below. There are two options because the record contains semicolons, and some DNS providers escape semicolons for you while others require you to do it when setting up the record.
With semicolons escaped:
v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB\;
With semicolons unescaped:
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
Comments
0 comments
Please sign in to leave a comment.