Summary
Brevo (formerly Sendinblue), like some other email service providers (ESPs), does not offer full SPF alignment for all users, particularly those on shared IP addresses. This means that while your emails might pass SPF authentication (the technical check), the domain in the 'Return-Path' header (used by SPF) may not align with the 'From' domain visible to recipients, potentially causing issues with DMARC alignment. This setup is often due to the complexities of managing the 'Envelope Sender' on shared infrastructure and the engineering effort required to enable per-domain customization.
Key findings
- Technical challenge: Brevo manages the 'Envelope Sender' domain for emails sent via shared IPs, which SPF uses for its check. This technical setup prevents full alignment with the customer's 'From' domain.
- Roadmap item: Brevo has indicated plans for 2025 to enable SMTP FROM domain customization for clients using shared IP addresses, aiming for complete domain alignment in email headers and body.
- Deliverability impact: While SPF misalignment can be a concern, its impact on deliverability is often mitigated if DKIM is properly aligned and passes DMARC. Many experts consider aligned SPF a 'nice-to-have' rather than a critical requirement when DKIM is robust.
- Dedicated IP solution: Brevo's support suggests using a dedicated IP for full alignment, but this is often impractical for senders with low email volumes (under 10k emails per month).
- Common practice: Some smaller ESPs also do not offer full SPF alignment, indicating it's not unique to Brevo.
Key considerations
- DMARC importance: Ensure your DMARC record is correctly configured and that at least one of SPF or DKIM aligns with your 'From' domain to pass DMARC. For more details, see our guide on DMARC, SPF, and DKIM.
- DKIM alignment: Prioritize DKIM alignment. If DKIM is aligned and passes DMARC, the lack of SPF alignment is generally less critical.
- Sender reputation: Even with partial SPF alignment, maintaining a strong sender reputation through good sending practices (low bounce rates, high engagement) is paramount. Learn how email authentication impacts deliverability.
- Monitor reports: Regularly review your DMARC reports to understand how your emails are being authenticated by various mailbox providers and if any issues arise due to SPF or DKIM failures. You can also refer to this Brevo deliverability review.
What email marketers say
Email marketers using Brevo have expressed concerns about the lack of full SPF alignment when using shared IPs, particularly when their deliverability checkers show errors. While acknowledging that Brevo's support suggests dedicated IPs for full alignment, marketers with lower sending volumes find this solution impractical. Many are aware that other ESPs also face similar challenges or have already implemented full alignment, and they look forward to Brevo's planned updates.
Key opinions
- Checker errors: Marketers frequently encounter SPF alignment errors when using online checkers, which can be confusing given emails are still delivered.
- Volume dependency: The suggestion of a dedicated IP for full SPF alignment is often unsuitable for those sending less than 10,000 emails per month due to cost and volume requirements.
- Similar issues elsewhere: Some marketers note that other major ESPs, like Mailchimp, also do not offer full SPF alignment on shared IPs.
- Hope for updates: There is anticipation and welcome for Brevo's stated intention to implement full domain alignment for shared IP users in 2025.
Key considerations
- Understanding alignment: Even if SPF doesn't align, it's important to understand why SPF passes in headers but not Google Postmaster Tools to avoid unnecessary worry.
- Focus on DMARC pass: The primary goal is for your emails to pass DMARC authentication. If DKIM aligns and DMARC passes, the deliverability impact of SPF misalignment is usually minimal. For more information, see Brevo's deliverability performance.
- Customer support: Be prepared that ESP support may not always offer solutions tailored to low-volume senders when discussing advanced authentication features.
Marketer view
A marketer from Email Geeks indicates that Brevo does not offer full SPF alignment, causing errors in external checkers. They note that most other ESPs seem to provide this feature.
Marketer view
A marketer from Email Geeks notes that Brevo's support suggested a dedicated IP for full SPF alignment, but this solution is impractical for their low volume of less than 10,000 emails per month.
What the experts say
Email deliverability experts generally agree that while full SPF alignment is ideal, its absence is not a critical deliverability issue as long as DKIM is properly configured and DMARC passes. The challenge for ESPs in providing full SPF alignment often stems from the technical complexities of managing the Envelope Sender for shared IP infrastructure, requiring significant coding, management, and customer support overhead to retrofit such a feature. However, many experts acknowledge that mailbox providers increasingly prefer comprehensive authentication signals, making full alignment a valuable enhancement.
Key opinions
- DKIM priority: As long as DKIM is aligned and passes DMARC, the lack of SPF alignment poses no real concern; it's considered a 'nice-to-have' feature.
- Implementation complexity: Providing full SPF alignment requires substantial coding, management, and ongoing customer support, especially for DNS configurations.
- Retrofitting challenges: It's far more difficult and resource-intensive to retrofit full SPF alignment into an existing ESP system than to design it from the ground up.
- Common question: SPF alignment issues with ESPs are a very common topic of discussion and concern among senders.
- Brevo's plans: A Brevo representative noted that providing complete domain alignment in email content (headers and body) is a main objective for 2025.
Key considerations
- Prioritize DMARC: Ensure that your DMARC policy is set up correctly, as DMARC relies on either SPF or DKIM alignment. Explore why emails go to spam from DMARC, SPF, DKIM alignment failures.
- Shared IP challenges: Understand that shared IP environments inherently limit the extent of SPF alignment an ESP can offer due to the nature of the 'Envelope Sender'.
- Customer DNS management: ESPs providing full SPF alignment often deal with customers incorrectly configuring their DNS records, which can break authentication and signal flow.
- Holistic deliverability: While SPF alignment is a factor, overall deliverability relies more heavily on sender reputation, list hygiene, content quality, and consistent DMARC compliance. A deeper discussion on SPF alignment importance is available.
Expert view
An expert from Email Geeks explains that Brevo's product team has a roadmap item for 2025 to allow SMTP FROM domain customization. This change will enable clients on shared IPs to achieve full domain alignment.
Expert view
An expert from Email Geeks notes that many smaller ESPs do not offer aligned SPF, indicating it is not an unusual practice. They clarify that as long as DKIM is aligned, there is no real concern, classifying SPF alignment as a 'nice-to-have'.
What the documentation says
Official documentation from email authentication and ESP platforms clarifies that SPF's authentication process relies on the 'Envelope Sender' (also known as the Return-Path or MailFrom) rather than the 'From' header seen by recipients. When an ESP like Brevo manages this 'Envelope Sender' domain on its internal servers (especially for shared IPs), it inherently leads to SPF passing but not aligning with the customer's 'From' domain. While this setup is technically compliant with SPF's design, it can impact DMARC alignment, which requires congruence between the 'From' header and at least one of the authenticated domains (SPF or DKIM).
Key findings
- Envelope sender: SPF authentication processes the Envelope Sender, not the 'From' address, which is typically managed by the ESP's internal server for shared IPs.
- Impact on ISPs: Using an 'unrelated domain' (i.e., one that doesn't align via SPF or DKIM) can raise red flags with ISPs, potentially leading to negative deliverability impacts.
- Dedicated IP for alignment: Setting up a dedicated IP address with an ESP typically allows for full SPF alignment, as the Envelope Sender can then match the customer's domain.
- Single SPF record: A domain can only have one SPF record, meaning ESPs must consolidate their sending IPs within that single record if they want to offer full alignment.
Key considerations
- DMARC alignment rules: DMARC requires either SPF or DKIM to align with the 'From' domain. If SPF is handled by the ESP's domain, DKIM becomes the critical path for DMARC success. Read more on how bad SPF alignment affects deliverability if DMARC passes.
- Domain reputation: Even without full SPF alignment, maintaining a positive domain reputation with consistent authentication and good sending practices is crucial. This is particularly important because Brevo uses its own server for the Envelope Sender, as outlined in this guide on configuring authentication for Brevo.
- Dedicated IP viability: Evaluate whether your email volume justifies the investment in a dedicated IP to achieve full SPF alignment.
Technical article
Documentation from AutoSPF.com explains that Brevo does not provide an SPF record because the SPF authentication process utilizes the Envelope Sender. This is managed directly by Brevo's internal server, which is standard for shared IP configurations.
Technical article
Documentation from Brevo's Help Center warns that using an unrelated domain can trigger red flags with ISPs. Such a practice negatively impacts email deliverability, emphasizing the need for proper domain association.
Related resources
5 resources
Related pages
Why does SPF pass in headers but not Google Postmaster Tools, and what are domain alignment best practices?
Why do my emails go to spam due to DMARC, SPF, and DKIM alignment failures?
Does SPF alignment with aspf=strict provide email deliverability benefits over aspf=relaxed?
What does it mean when SPF is not aligned in a DMARC report and how does it affect deliverability?
How does bad SPF alignment affect email deliverability if DMARC authentication passes?
A simple guide to DMARC, SPF, and DKIM
Why you shouldn't add MailChimp to your SPF record
Why your emails fail: expert guide to improve email deliverability [2025]
