Online Express (OLX) FAQs

Delivery and deliverability

Delivery refers to whether a mailbox provider accepts a message. Deliverability refers to how a mailbox provider determines where to place a message, such as in the recipient's inbox or SPAM folder.

The IP addresses we use to send bulk email include these ranges:

  • 205.139.104.0/22 (205.139.104.1 - 205.139.107.254)

  • 216.235.196.0/22 (216.235.196.1 - 216.235.199.254)

  • 216.235.200.0/21 (216.235.200.1 - 216.235.207.254)

To ensure your anti-SPAM systems don't filter out email you send to yourself from our servers, we recommend you work with the administrator of your network’s email system to whitelist the following ranges of IP addresses:

  • 205.139.104.0/22 (205.139.104.1 - 205.139.107.254)

  • 216.235.196.0/22 (216.235.196.1 - 216.235.199.254)

  • 216.235.200.0/21 (216.235.200.1 - 216.235.207.254)

Also, to help mailbox providers — including the receiving mail server for your organization — verify that you are a legitimate sender, our email system supports multiple authentication methods for your domain. Since you own your domain, we rely on you to manage the authentication for it.

If you signed up to receive email notifications for online transactions but are not receiving them, follow these steps to determine the cause:

  1. Confirm the form is configured to send notifications to the email address.

    • From the form in your Online Express plugin, select Edit, and then select the • From the form in your Online Express plugin, select Edit, and then select the Thank yous tab. Thank yous tab.

    • Confirm the user’s email address appears in the Receive email notifications for new donations panel. If not, enter it and select Save & Close.

  2. To help mailbox providers — including the receiving mail server for your organization — verify that you are a legitimate sender, configure authentication for your domain.

  3. To ensure your anti-SPAM systems don't filter out email you send to yourself from our servers, work with the administrator of your network’s email system to whitelist the following ranges of IP addresses:

    • 205.139.104.0/22 (205.139.104.1 - 205.139.107.254)

    • 216.235.196.0/22 (216.235.196.1 - 216.235.199.254)

    • 216.235.200.0/21 (216.235.200.1 - 216.235.207.254)

  4. Contact Support if these steps don’t resolve the issue and provide the following:

    • The names of the specific forms that are not sending them

    • The specific email addresses that are not receiving them

    • Whether users ever received them. If so, when they first noticed they weren’t receiving them.

    • For users who only receive some of the emails, the specific transactions that did not send a notification email and include the donor name, transaction date, and transaction amount.

Follow these steps to determine the cause:

  1. If the email address is for a constituent, confirm:

    • Deceased and Requests no email are not selected on the Bio 1 tab of the record.

    • Inactive and DNC are not selected in the Contact Information section.

    • The constituent record is included in the query used in the email list selected for the email blast.

  2. If it’s for a relationship, confirm:

    • The relationship record is linked to a constituent record in the query results of the query you used in your email list.

    • Inactive and DNC are not selected in the Contact Information section.

    • The relationship record is one of the relationship types selected in the email list selected for the email blast.

  3. Otherwise, confirm the email address is:

    • One of the types selected in Account > Integration Options> Email mapping in the Online Express plugin

    • Not present in the Unusable emails list

    • Not present in the recipient’s SPAM folder

  4. Contact Support if these steps don’t resolve the issue.

Processing

As an email service provider (ESP), Blackbaud's sending system is robust and scales well for clients both large and small. Since our system can send large numbers of messages simultaneously, we conform to standards for high-volume senders to ensure email delivery.

To maintain favorable reputations with mailbox providers, our system reviews recipient lists and automatically suppresses email addresses for the following reasons:

  • Hard bounces — When email delivery fails, mailbox providers send bounce code responses. The system categorizes and tracks these bounce codes so that it can suppress email addresses when they fail, such as when a recipient's address is invalid or their account is closed.

  • SPAM complaints — Our email specialists help maintain Feedback Loop (FBL) agreements with mailbox providers that offer FBL programs. With an FBL agreement, a mailbox provider agrees to inform us when a recipient marks a message as unsolicited — such as when they select a "This is SPAM" button or link — so that our system can suppress their email address from future mailings from that sender.

  • Opt-out links — When a recipient uses an opt-out link in a message to request removal from future emails, our system suppresses their email address from future mailings specific to their request, such as only for a particular newsletter or all emails from an organization.

Since Blackbaud doesn't control your organization's domain, email sent from Online Express isn't technically sent from your @domain.org domain, even though you may have entered it in the "send as" or "send from" email address field. Email messages are actually sent from Blackbaud's Mail Transfer Agent (MTA) servers. As a result, receiving mail servers may not recognize the domain.

To help mailbox providers — including the receiving mail server for your organization — verify that you are a legitimate sender, our email system supports multiple authentication methods for your domain. Since you own your domain, we rely on you to manage the authentication for it.

Also, to ensure your anti-SPAM systems don't filter out email you send to yourself from our servers, we recommend you work with the administrator of your network’s email system to whitelist the following ranges of IP addresses:

  • 205.139.104.0/22 (205.139.104.1 - 205.139.107.254)

  • 216.235.196.0/22 (216.235.196.1 - 216.235.199.254)

  • 216.235.200.0/21 (216.235.200.1 - 216.235.207.254)

When an email bounces, Online Express does not update Raiser’s Edge. Instead, we automatically remove emails that hard bounce from future mailings.

Note: We do not remove email addresses that soft bounce from future mailings. To determine which emails hard or soft bounced, compare the Unsubscribe email list and the bounces in the email stats.

When a constituent opts out of receiving messages from your organization (unsubscribes), the request is included in the response to the Appeal on the constituent’s record when you add email stats from Online Express to the record. It’s important to note Online Express doesn’t select:

  • Do Not Contact (DNC) on the Phone/Email record in The Raiser's Edge

  • Requests no emailon the Bio 1/Org 1 tab because a constituent might opt-out of mass marketing, but still want to receive other emails from your organization.

Note: Online Express doesn’t consider out of office replies as bounces or opt outs.

Best practices

To ensure mailbox providers place your messages in recipient inboxes, and to improve engagement, we recommend you follow our recommended best practices.

The Sender Policy Framework (SPF) protocol is an authentication method that enables receiving mail systems to verify the mail servers that are authorized to send email on behalf of a domain.

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 the following to your TXT record for your SPF information:

+include:outboundmail.blackbaud.net ~all

Note: If your TXT record includes older entries such as include:outboundmail.blackbaudhost.com, blackbaudemail.netcommunity1.com, or Blackbaud's IP ranges, remove them.

The DomainKeys Identified Mail (DKIM) protocol is an authentication method that digitally signs part of an email message so that receiving mail systems can verify it wasn’t altered after it was originally sent.

To use it, a sender decides which elements of a message they want to include for the signature — such as the header and body or individual fields in the header — and then configures their system to encrypt those selections with a private key when they send email. When a mailbox provider receives a message with a DKIM signature, they use the public key the sender lists for their domain in the DNS to “unlock” the private key.

To request a custom DKIM signature, contact Support and provide your domain and site ID.

We encourage you to follow these deliverability recommendations.

Content filters like SpamAssassin score email content so mailbox providers can classify and filter unwanted messages. To avoid issues with them, create subject lines that don't use numbers or special characters, and avoid exaggerations such as ALL CAPS, overused exclamation points, and stars or dotted lines. Also, avoid terms such as "Free", "Apply now", "Extra cash", "Home-based", "Opportunity", "Limited time", "Money", and any words that may be considered pornographic. Since anti-SPAM filters also assess message content after they review subject lines, use these same guidelines when you create the body of your emails.

We also recommend you review all of our email best practices.

Note: For an exhaustive list of words to avoid, see HubSpot's The Ultimate List of Email SPAM Trigger Words.