Why doesn't Brevo offer full SPF alignment and how much does it impact deliverability?

Brevo's lack of full SPF alignment, often due to shared IP configurations, is a multifaceted issue impacting email deliverability. While DKIM alignment is consistently highlighted as a more critical factor for DMARC compliance and overall deliverability, SPF alignment contributes to improved sender reputation and DMARC compliance. The absence of full SPF alignment stems from factors such as technical debt, the prioritization of other features, the complexity of managing SPF records across multiple domains on shared IPs, and the coding/management/support overhead involved in retrofitting this capability. The impact on deliverability varies based on sending volume and recipient domain policies; low volumes may not be significantly affected, while larger volumes can experience negative consequences. Experts and marketers suggest monitoring deliverability metrics, ensuring proper DKIM alignment, and considering dedicated IPs or alternative ESPs if issues arise. Brevo's product team has this on their roadmap for 2025.

Brevo's lack of full SPF alignment, often due to shared IP configurations, raises deliverability concerns. While DKIM alignment is considered more critical, SPF alignment contributes to sender reputation. Reasons for not offering full SPF alignment include technical debt, prioritization of other features, and the complexity of managing SPF records across multiple domains. The impact on deliverability varies based on sending volume and recipient domain policies, with larger volumes potentially facing negative consequences. Several email marketers suggest monitoring deliverability metrics, using DKIM alignment as a primary strategy, and considering dedicated IPs or alternative ESPs if issues arise. There is a suggestion that Brevo is looking to address SPF alignment in the near future.

Several experts suggest that Brevo's lack of full SPF alignment isn't unusual among smaller ESPs. While desirable, DKIM alignment is often considered more critical for achieving DMARC compliance and maintaining deliverability. The absence of full SPF alignment is often attributed to the complexity of implementing and managing it, especially as a retrofit to existing ESP infrastructure. This involves significant coding, management, and customer support overhead. Properly setting up SPF records can be complex and challenges can arise.

Documentation indicates that Brevo's partial SPF alignment, particularly with shared IPs, exists because DKIM is prioritized. For DMARC compliance and increased deliverability, aligning SPF with the 'MAIL FROM' domain is essential. Failure to do so can result in failed DMARC checks and potential spam or rejection of emails. Using a dedicated IP is recommended for full SPF alignment, especially for high-volume senders.