Summary
The responses address the usage of Validity's FBLs, the status of Comcast data, and the implementation of DKIM FBL. AWeber opted out of Validity's FBLs due to perceived ineffectiveness and desires access to Comcast data. DKIM FBL v2 is released, with AWeber showing interest, but the initial draft needs more feedback and development. Monitoring DNS records is suggested as an alternative to routing reports. Major ESPs generally support FBLs, although the reporting quality varies among ISPs. Validity offers FBL aggregation services. FBLs, governed by ARF standards, are crucial for identifying problematic addresses, managing sender reputation, and enhancing deliverability. Comcast blocks senders with poor engagement, emphasizing list hygiene and engagement monitoring. DKIM enhances email authentication, but its impact on deliverability depends on ISP spam filtering algorithms.
Key findings
- AWeber's Stance: AWeber has not adopted Validity's FBLs due to their perceived limitations and expresses interest in Comcast data.
- DKIM FBL Progress: DKIM FBL v2 is available, but the initial draft needs further refinement and adoption.
- FBL Support Landscape: Most major ESPs support FBLs, but the quality of reporting varies considerably among ISPs.
- ARF Standards: Feedback loops are governed by ARF standards, facilitating standardized abuse reporting.
- Comcast Blocking: Comcast implements blocking based on low engagement or high complaint rates.
- Validity's Role: Validity offers feedback loop reporting services, centralizing FBL data.
- DNS Monitoring Alternative: Monitoring DNS records provides a simpler alternative to routing reports for assessing FBL status.
Key considerations
- Varying ISP Reporting: The quality and extent of feedback loops vary widely across different ISPs.
- Holistic Approach: Employing FBLs alongside other deliverability best practices helps to optimize email performance.
- Data-Driven Optimization: Actively monitoring and responding to FBL data, along with other engagement metrics, is crucial for maintaining a positive sender reputation and high deliverability rates.
- List Hygiene Practices: Regularly cleaning and maintaining your email list helps avoid blocks and improve overall engagement.
- Implementation Considerations: Successfully implementing DKIM-FBL requires community involvement and ongoing code improvements.
What email marketers say
13 marketer opinions
The question focuses on which ESPs utilize Validity's Feedback Loops (FBLs), the status of Comcast data, and the progress of DKIM FBL implementation. AWeber has not signed up for Validity's FBLs due to their perceived ineffectiveness. While major ESPs generally support FBLs to manage sender reputation, the level of reporting varies significantly among ISPs. DKIM FBL v2 has been released, with AWeber expressing willingness to implement it. The DKIM FBL draft is still under development, lacking substantial feedback and coding efforts. Monitoring DNS records is suggested as an alternative to routing reports. Validity offers an FBL reporting service, and various sources highlight the crucial role of FBLs in identifying problematic addresses, reducing spam complaints, and improving sender reputation and email deliverability.
Key opinions
- FBL Support: Most major ESPs support Feedback Loops (FBLs) to help senders manage their reputation by identifying users who mark emails as spam.
- Validity's Role: Validity offers a Feedback Loop Reporting service that aggregates FBL data, emphasizing the importance of FBLs for removing problematic recipients.
- DKIM FBL Status: DKIM FBL v2 has been released, but the draft version is still under development and lacks substantial feedback.
- Comcast Data: AWeber wishes they could get Comcast data, suggesting it's a valuable but currently inaccessible resource.
- AWeber's Implementation: AWeber has not signed up for Validity's FBLs, citing their ineffectiveness, but expresses willingness to implement DKIM FBL.
- DNS Monitoring: Monitoring DNS records is suggested as a simpler alternative to routing reports for assessing FBL implementation.
Key considerations
- Varied ISP Support: The level of feedback loops provided by ISPs varies heavily, with some offering basic or no reporting.
- DKIM Impact: While DKIM is crucial for authentication, its direct impact on deliverability depends on how ISPs use it; FBLs provide valuable insight into these processes.
- Ongoing Process: Maintaining good deliverability and sender reputation requires ongoing monitoring and action based on FBL data.
- Proactive Management: Actively participating in FBLs helps identify and remove problematic addresses, reducing spam complaints and improving sender reputation.
- Implementation Efforts: Implementation of new standards, like DKIM FBL, requires industry feedback and coding efforts to be effective.
Marketer view
Email marketer from Mailjet.com details the importance of using FBLs to maintain sender reputation by helping identify and remove subscribers who mark messages as spam, which improves email deliverability rates.
26 Nov 2021 - Mailjet.com
Marketer view
Marketer from Email Geeks shares that AWeber didn't sign up for Validity's FBLs because it hasn't changed anything. They wish they could get Comcast data, as the other FBLs provide a tiny trickle of data that doesn't matter.
23 Jun 2022 - Email Geeks
What the experts say
2 expert opinions
The provided answers relate to feedback loops (FBLs) and Comcast's email policies. FBLs are mechanisms through which ISPs inform senders about spam complaints, allowing them to identify and remove problematic addresses, thus enhancing deliverability. Comcast is known to block senders with low engagement or high complaint rates, highlighting the importance of maintaining clean email lists and actively monitoring engagement metrics to prevent being blocked.
Key opinions
- FBL Functionality: Feedback loops (FBLs) enable ISPs to notify senders of spam complaints, aiding in identifying and removing problematic email addresses.
- Comcast Blocking: Comcast blocks senders who exhibit low engagement or generate high complaint rates.
Key considerations
- List Hygiene: Maintaining a clean and engaged email list is crucial for avoiding blocks and ensuring high deliverability.
- Engagement Monitoring: Actively monitoring engagement metrics is necessary to identify and address potential issues before they lead to blocking.
- FBL Participation: Actively participating in FBLs is essential for understanding and addressing recipient complaints, thereby improving sender reputation and deliverability.
Expert view
Expert from Spam Resource explains that Comcast is known to block senders due to low engagement or high complaint rates. Maintaining a clean list and monitoring engagement are crucial for avoiding blocks.
22 Jan 2022 - Spam Resource
Expert view
Expert from Word to the Wise explains that feedback loops (FBLs) are provided by ISPs to let senders know when recipients mark their messages as spam. Participating in FBLs helps senders identify and remove problematic addresses from their lists, improving deliverability.
25 Oct 2023 - Word to the Wise
What the documentation says
4 technical articles
The provided documentation references highlight the importance of feedback loops (FBLs) and DKIM in email deliverability. RFC-Editor.org outlines standards for abuse reporting (ARF) used in FBLs. The IETF details the DKIM-FBL specification, enabling disposition reporting via DKIM signatures. Sourceforge.net emphasizes FBLs' necessity for monitoring DKIM-signed email. Google Support underscores consistently monitoring and acting on FBL data to maintain deliverability and a positive sender reputation, especially with Gmail users.
Key findings
- ARF Standard: RFC-Editor.org outlines official standards for managing abuse reporting using ARF within feedback loops.
- DKIM-FBL Spec: The IETF details the DKIM Feedback Loop (DKIM-FBL) specification, enabling reporting of message disposition via DKIM signatures.
- FBL Necessity: FBLs are necessary for monitoring DKIM-signed email delivery and resolving deliverability issues.
- Google's Emphasis: Google Support states that consistently monitoring and acting on feedback loop data is vital for maintaining deliverability and sender reputation with Gmail users.
Key considerations
- Standard Compliance: Adhering to standards such as ARF is important for proper abuse reporting in FBLs.
- DKIM-FBL Utilization: Implementing DKIM-FBL specifications can provide valuable insights into message disposition.
- Active Monitoring: Continuously monitor and act upon FBL data to maintain optimal deliverability and sender reputation.
- DKIM Synergy: Using DKIM in conjunction with FBLs allows you to take a proactive approach to email deliverability and sender authentication
Technical article
Documentation from sourceforge.net, although discussing dkimproxy, explains how DKIM works and the necessity for FBLs to monitor DKIM-signed email delivery and resolve deliverability issues.
16 Jul 2021 - sourceforge.net
Technical article
Documentation from IETF details the DKIM Feedback Loop (DKIM-FBL) specification that enables reporting of message disposition back to the sender based on DKIM signatures.
10 Dec 2023 - datatracker.ietf.org
Are abuse reports and feedback loops (FBLs) still useful in email marketing, and how do they work with different email clients?
Can ESP clients sign up for Validity FBL and how do they validate their IPs/domains?
How can I accurately monitor complaint rates for email marketing using Google Postmaster Tools, Yahoo FBL, and my ESP?
How can I contact Yahoo's postmaster team for FBL access and troubleshoot setup issues?
How do ESPs collect Yahoo FBL data using double DKIM signing?
How do I decode Comcast FBL email address to unsubscribe users?
