Bluetie performs anti-spam and virus checking for all messages. We also support both SPF and DKIM, which are additional anti-spoofing measures that can greatly reduce the chance that spoofed messages claiming to be sent from your domain are delivered. For this reason, we highly recommend that you set up both SPF and DKIM for your domain.
SPF (Sender Policy Framework) is an email validation system designed to detect email “spoofing” (a technique commonly used by spammers to send spam and phishing messages using forged return addresses), and to prevent the delivery of such messages.
Setting up SPF involves the creation of a DNS TXT record that specifies which host systems are authorized to send mail on behalf of the domain. Email service providers then check for published SPF records to determine how to handle delivery (e.g., only messages sent from a host authorized in the SPF record are delivered), so once in place it can be an effective anti-spam technique.
To get SPF in place, you will need to create a valid DNS TXT record through your DNS provider’s domain record management system (you may need to contact your domain registrar or provider for assistance with this). You will need to create the following SPF records (depending upon which type of Bluetie accounts you have):
If you have only standard Bluetie Executive type accounts, create the following SPF record:
v=spf1 include:spf.bluetie.com -all
If you have only Hosted Exchange type accounts, create the following SPF record:
v=spf1 include:spf.serverdata.net ~all
For additional information regard SPF, please refer to the following: OpenSPF FAQ
DKIM (DomainKeys Identified Mail) is an email authentication system designed to detect email spoofing by allowing the sender of an email to digitally sign the email message, so that the recipient of the message can verify that it was authorized by the owner of that domain.
In DKIM, the email system sending a message on behalf of that domain signs all or part of the message using a private key, and the recipient mail systems then verifies the signature via a publicly published DNS TXT record. The recipient mail system then determines how to handle treatment or delivery of the message based on their policy.
Due to the configuration necessary for this to work within the Bluetie system, there is a single-time set up fee for initial implementation. If you would like to have us configure DKIM support for your domain, please let us know by contacting us at firstname.lastname@example.org!
For additional information regarding DKIM, please refer to the following: DKIM