When a mailbox provider uses SPF authentication, they compare the server that appears in the message header — also known as the long or internet header — to the sending servers that are listed in the Domain Name System (DNS) record for the “envelope from” address.
To authorize our system to send emails on your behalf, access the DNS record for your domain through your domain name registrar — such as GoDaddy, Network Solutions, or Name.com — and add a TXT record to it for your SPF information.
Note: Add a TXT record with SPF information for each domain you use to send email.
If your organization uses its own office email server and Blackbaud is the only ESP that sends email on your behalf, enter:
v=spf1 +include:outboundmail.convio.net +include:outboundmail.blackbaud.net ~all
If your organization uses multiple ESPs, enter:
v=spf1 +mx +include:outboundmail.convio.net +include:outboundmail.blackbaud.net ~all
Tip: Don’t forget to also include the other email servers that are authorized to send on your behalf.
Sender ID and Sender Policy Framework (SPF) are two methods of email authentication that enable organizations to specify which mail servers are authorized to send email in their name. While both are similar, Sender ID is actually a variation of SPF developed by Microsoft.
Email publishers add a TXT record to the Domain Name System (DNS) and identify the authorized mail servers. When an Internet Service Provider (ISP) receives email, it looks up the information associated with the domain sending the message; this is where Sender ID and SPF come into play.
If the mail server sending the email is on the domain’s list of authorized mailers, the recipient system treats the email as legitimate. If the mail server is not on the authorized list, the recipient system treats the email as suspicious and anti-spam filters take over because the system can’t confirm the mail can be trusted.
SPF is based on verifying the "Return-Path" header from an email, which is also called the "envelope sender," but users typically don't see this address. Sender ID works similarly, but uses the "From" address of an email that is displayed instead. To help you fully understand the difference, we'll explain how both methods treat email sent from Luminate Online.
SPF checks the envelope from address, which is always a Convio.net address, which looks up the DNS record to ensure Convio.net is authorized. Sender ID checks the message's from address, which is usually a client provided email address, and looks up the DNS record of the organization sending the email to see if Convio mail servers are authorized to send email in its name.
Yahoo! implemented their own email verification standard called DomainKeys, which is necessary for email delivery to recipients using Yahoo as an ISP. For information about configuring Domains, see DomainKeys Identified Mail (DKIM).
Our applications continuously test the domains you use to send email from our system for compliance with DomainKeys and Sender ID. However, different ISPs have different standards, and it's important that your organization implement both.
Note: Unlike DomainKeys, failure to comply with Sender ID does not require any changes to your email.