Upcoming change to email sending: Keep your emails on track

Sender Policy Framework (SPF) overview

Finalsite enforces Sender Policy Framework (SPF) authentication for all outbound emails. This helps verify that messages are sent from authorized sources and protects your domain’s reputation. If an email is sent from a domain that doesn’t include Finalsite’s SPF entry, the “From” address is automatically replaced with noreply@finalsiteconnect.com. The message will still be delivered, but the sender identity shown to recipients may be impacted.

What to check

• Do you require emails to be sent from a specific domain (e.g. info@school.org)?
• Does your domain already have an SPF record set up?

If you answered YES to either of those questions, you will want to check whether Finalsite’s SPF entry (include:spf.finalsiteconnect.com) is included.

What action should I take? 

If you don’t require custom sender domains, no changes are needed. 

If you do, work with your IT team to update your domain’s SPF record using the information in this section. 

Don't already have an SPF record? 

Add this TXT record:

• Type: TXT  
• Host/Name: @  
• Value:
  • v=spf1 include:spf.finalsiteconnect.com -all

Already have an SPF record?

Update it to include Finalsite’s entry:

• Example existing record before updating:
  • v=spf1 include:_spf.google.com -all
• Example record after updating:
  • v=spf1 include:_spf.google.com include:spf.finalsiteconnect.com -all

Conclusion

Adding Finalsite to your SPF record authorizes our system to send emails on your behalf and helps prevent messages from being flagged as spam or blocked by mail servers. If you need help, our Support team is here for you!