What ESPs use Validity's FBLs and what is the status of Comcast data and DKIM FBL implementation?
Summary
What email marketers say13Marketer opinions
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.
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.
Marketer from Email Geeks explains that the draft has received minimal feedback, and could change substantially. They would have a hard time convincing anyone to code that up until it progresses.
Email marketer from EmailToolTester.com explains that FBLs offer many benefits, including identifying problem addresses, reducing spam complaints, and improving sender reputation. Also states it helps maintain high deliverability rates with major ISPs.
Email marketer from StackExchange notes that while DKIM is crucial for authentication, its direct impact on deliverability depends on how ISPs use it in their spam filtering algorithms. FBLs provide valuable insight into these processes.
Email marketer from EmailDeliverability.com states FBLs are essential for understanding your sender reputation because they reveal how recipients perceive your emails, affecting deliverability and inbox placement.
Email marketer from Litmus details the need for FBLs to monitor spam complaints, manage sender reputation, and improve email deliverability. They note it's an ongoing process that's critical for maintaining good relationships with ISPs.
Marketer from Email Geeks says that monitoring DNS records is easier than routing reports and anyone could do it if they have the information from DKIM signatures, adding that current numbers are likely 0.
Marketer from Email Geeks, Tom Kulzer, mentions the release of DKIM FBL v2 and AWeber's willingness to implement it, followed by Marketer Alex Brotman inviting others to share feedback. Kulzer describes the DNS update as trivial, Brotman agreeing that it depends on self-created needs but can be flexible while easy for most use cases.
Email marketer from Validity.com shares that Validity offers a Feedback Loop Reporting service which aggregates FBL data from participating ISPs. While not listing specific ESPs, they emphasize the importance of FBLs for identifying and removing problematic recipients.
Email marketer from Kickbox.com explains that most major ESPs support feedback loops (FBLs) to help senders manage their reputation by identifying users who mark their emails as spam.
Email marketer from SparkPost.com details the process of setting up feedback loops (FBLs) with various ISPs, including those that provide aggregated reporting. They explain how to register with each ISP individually to receive abuse reports.
Email marketer from Reddit says that the level of feedback loops that ISPs provide varies heavily, with some only offering very basic reporting, and others offering advanced reporting. Some may not offer any.
What the experts say2Expert opinions
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.
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.
What the documentation says4Technical articles
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.
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.
Documentation from RFC-Editor.org outlines the official standards for managing abuse reporting using ARF (Abuse Reporting Format), which are utilized in feedback loops to communicate spam complaints.
Documentation from Google Support states that consistently monitoring and acting on feedback loop data is necessary to maintain high deliverability rates and a positive sender reputation with Gmail users.