Email Whitelisting

The BrightArrow interface allows you to send emails as if they were coming from your own email domain. This is a great way to make sure your intended recipients see the message as something from you rather than something that looks like spam. While the email looks like it comes from you it actually is sent from the BrightArrow servers. This is a common technique used by phishing sites trying to trick people into clicking on a fake list to gather their personal information and as such many email clients will now see these emails as junk mail.

When you send through BrightArrow you are not phishing, you’re sending valuable information to specific people. In order to increase the likelihood of your message not being automatically added to someone’s spam folder we suggest updating your email service to know that you are allowing valid emails to come through our servers on your behalf.

The best solution is to add our SPF reference into your SPF record.  It is done in your DNS records in the form of a specially formatted TXT record.  Are you familiar with SPF records?

We have a consolidated SPF reference that you can use:

include:spf_target.brightarrow.com

For example, you could have the following as your entire SPF record if it contains Google and BrightArrow:

v=spf1 include:_spf.google.com include:spf_target.brightarrow.com ~all

Once you have this SPF record in place, we also have to make a minor change on our side to change the originating address reference.  Let us know once you have updated your DNS record so we can change the email header accordingly from our side. 

One important point – we cannot be making our change until we hear from you that you have made your change.  Once you have verified your change is made, let us know and we’ll change it on our side and verify that the email header information is correct. 

Once your servers are updated and our servers are as well then many more of your recipients will receive your emails in their inbox rather than their spam folders.

We do not have specific directions for all DNS providers however we have put together an example for users of Network Solutions:

SPF Setup Instructions: Network Solutions

Sending from your domain vs replying to your domain

BrightArrow gives you the option of sending from your domain using our servers or allowing our servers to send as BrightArrow but setting the reply to portion of the email to your domain. There are pros and cons to each. Below are some things to keep in mind when making that decision for yourself.

Default Setting - send and reply using default BrightArrow address

By default the servers will send as Notification-Do_Not_Reply@brightarrow.com. Do nothing to set this up.

Pros Cons
Email is sent from a BrightArrow server AS a BrightArrow email address. This reduces the chance your email appears as spam to recipient’s filters The email address won’t mean much to your recipients as they know you but probably don’t know BrightArrow.
Feedback (failed attempts, bad email addresses, etc) comes back to our server and is included in the reports Replies go back to our server so you will never see them.

Sending as your own domain

By adding our information to your spf record (see above) we can send email from our server as if we are your server. Once the SPF record is updated and someone from BrightArrow has made the necessary changes you can change your default email addresses in the user settings as seen below.

Pros Cons
Email address is from your organization which is likely recognizable by your recipients Feedback (failed attempts, bad email addresses, etc) is sent to the sending address. This can be very alarming when a mass message suddenly creates many responses back to the sender.
With SPF in place our server is “allowed” to send on your behalf so  Finding real replies amongst all the feedback could be time consuming

Using your domain as the reply to

The third option is a hybrid of these. You do not need to update your spf record as the server will continue to use the Notification-Do_Not_Reply@brightarrow.com email address as the sender. However the email address from your domain will be used as the reply to address. In this way bounces come back to us and can be included in the report but real replies get sent back to you.

Pros Cons
Emails coming from the BrightArrow server as a BrightArrow email address are less likely to be seen as spam by filters The email address won’t mean much to your recipients as they know you but probably don’t know BrightArrow.
Feedback (failed attempts, bad email addresses, etc) comes back to our server and is included in the reports
Replies go back to the email address entered. This means you’ll only get real email replies, not all of the server feedback.
Your SPF record does not need to be updated. This method can be used right away, no extra setup.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.