SimplyCast has adopted Sender Policy Framework (SPF) for all campaigns sent using our system. This framework has many benefits for you as a marketer and to your user as the recipient of the message.
The main benefit of adopting SPF is that it prevents abusers to fake your email address; hence, email filters will more than likely allow your email to pass to your recipient's inbox.
Some of the reasons why illegitimate senders want to avoid using SPF supported services is that they don't want to receive the delivery status notifications reporting non-delivery to their real address.
Furthermore, scammers want to impersonate well-known, trusted identities in order to conceal their scam and gain the trust to execute on the scam.
SimplyCast has adopted this leading-edge technology to deliver the highest delivery possible for your campaign.
How do we do this?
At SimplyCast we have added this special address to the "Sender" field located within the email header information to allow mail servers to authenticate your message with our SPF records and ensure safe passage to your recipient's inbox. Please note the email clients such as Outlook don't care about the sender field. What they care about is the origin of the email and if it is legitimate or not.
In general, SPF is basically a verification layer that is easily accessible to verify if the user is allowed to send from a specific domain. For example, you can set your local Internet service provider's email address to @homtail.com and if you attempt to send your email using a non-compliant email address from your local ISP's server, most services will not accept your email.
Wondering what the difference between SPF and Sender-ID is? Sender-ID is a slight variant on the SPF standard that is promoted by Microsoft. Fortunately, it is not an either-or choice: systems can publish records for both Sender-ID and SPF.
To close on this subject, SPF restores confidence in the origin of email messages from the sending domains, which is another step forward in the right direction.