Basic checks for feedback loop (FBL) operation
Feedback loops (FBLs) are an automated mechanism for the forwarding of spam reports by individual mailbox users of major email networks like Outlook and Gmail. They enable bulk mail senders to automatically respond to mail recipients who mark individual messages as spam, eg by removing them from mailing lists, or suspending the sending user's account. The FBL reports can use standardised formats which may I code additional classification info like phishing or viruses. Usage of FBLs typically improved the deliverability of the sender's mail network as the large inbox providers can recognise that their users wishes are being automatically respected. Typically a dedicated mailbox on the sender side is used to receive email FBL reports, conventionally [email protected]. that address is then registered to receive FBL reports with the inbox providers like microsoft.
Therefore LMCC can check that a feedback loop address is setup and reachable. Eg check if an [email protected] address exists, and check that it can receive mail (eg not mailbox full or delivery errors). Detected problems here would deserve generation of a Local Insight.
In future more sophisticated FBL based functionality could be added, to ease the otherwise manual procedure of registering the FBL address with each inbox provider separately. See eg fbl.returnpath.net for an example of one attempt to centralise and ease this process. Screenshot: