Skip to main content

Feedback Loops

Manage subscribers who report your emails as abuse using Feedback Loops (FBL). The mailbox provider forwards the reported message to a designated email address, allowing you to suppress or remove the complaining user from your database.

Overview

Feedback loops process spam complaints automatically:

+------------------+      +------------------+      +------------------+
| RECIPIENT MARKS | ---> | ISP SENDS | ---> | FBL ADDRESS |
| EMAIL AS SPAM | | COMPLAINT | | RECEIVES |
+------------------+ +------------------+ +------------------+
|
v
+------------------+
| PROCESSING |
| - Parse email |
| - Find contact |
| - Flag: Spammed |
+------------------+
|
v
+------------------+
| NO FURTHER |
| EMAILS SENT |
+------------------+

Why Feedback Loops Matter

Sender Reputation

  • Reduce complaints - Stop sending to people who complained
  • ISP compliance - Meet ISP complaint rate requirements
  • Avoid blacklisting - High complaint rates trigger blocks
  • CAN-SPAM - Honor unsubscribe requests
  • GDPR - Respect recipient preferences
  • Best practices - Industry standard for email senders

List Quality

  • Automatic flagging - No manual intervention needed
  • Clean lists - Stop emailing contacts who complained
  • Better engagement - Focus on interested subscribers

How Feedback Loops Work

ISP Complaint Flow

  1. Recipient receives your email
  2. Recipient clicks "Report Spam" or "Junk"
  3. ISP records the complaint
  4. ISP sends complaint to registered FBL address
  5. Mumara processes the complaint
  6. Contact is flagged as Spammed and will not receive any further emails

Supported ISPs

Major ISPs that support feedback loops:

ISPFBL Program
Yahoo/AOLYahoo CFL Program
MicrosoftJMRP (Junk Mail Reporting Program)
ComcastComcast FBL
USA.netUSA.net FBL
FastmailFastmail FBL
OthersCheck individual ISP programs
Gmail

Gmail does not offer a traditional FBL program. Use Google Postmaster Tools instead.


Viewing Feedback Loops

Navigate to Setup → Feedback Loops to view all FBL addresses.

Page Features

  • Add New button to create an FBL address
  • Bulk Actions dropdown for batch operations
  • Show entries dropdown to control page size
  • Search box to find specific FBL addresses

Table Columns

ColumnDescription
FBL EmailThe email address receiving complaints
ComplaintsNumber of processed complaints (clickable to view details)
StatusActive/Inactive
Last ProcessedDate and time complaints were last processed
Created onDate and time the FBL address was created
ActionsRow action menu

Row Actions

Click the ... (three dots) menu on any row to access:

ActionDescription
EditModify FBL settings
DeleteRemove this FBL address

Viewing Complaints

Click the Complaints number to view processed complaints for that FBL address.


Creating a Feedback Loop Address

Navigate to Setup → Feedback Loops and click Add New.

Feedback Loop Settings

FBL Email *

Enter the email address registered with ISPs for feedback loops.

Examples:

Dedicated Address

Use a dedicated email address solely for FBL processing. Register this address with each ISP's feedback loop program.

Hostname *

Enter the IMAP or POP3 server address.

ProviderIMAP HostPOP3 Host
Gmailimap.gmail.compop.gmail.com
Outlookoutlook.office365.comoutlook.office365.com
Customimap.yourdomain.compop.yourdomain.com

Port *

Enter the server port number.

ProtocolPortSecurity
IMAP143None/STARTTLS
IMAP993SSL/TLS
POP3110None/STARTTLS
POP3995SSL/TLS

Username *

The login username for the email account (usually the full email address).

Password

The password for the email account (stored encrypted).

Folder *

Specify the mailbox folder to check for complaint emails.

Default: INBOX

Validate Certificate

Select whether to verify server SSL certificates.

OptionDescription
YesValidate certificate (recommended for production)
NoSkip validation (use for self-signed certificates)

Encryption

Select the connection security type.

OptionDescription
NoneNo encryption (not recommended)
SSLImplicit SSL/TLS encryption
TLSSTARTTLS encryption

Delete Emails after Processing

Select whether to remove complaint emails after they have been processed.

OptionDescription
YesDelete processed emails (recommended)
NoKeep emails in mailbox

Recommendation: Enable to prevent duplicate processing and keep the mailbox clean.

Email Protocol *

Select the mail retrieval protocol.

ProtocolDescription
POPPost Office Protocol
IMAPInternet Message Access Protocol (recommended)

Recommendation: IMAP is preferred for better message management.

Status

Toggle to enable or disable FBL processing. Inactive addresses are not checked for complaints.


Validating and Saving

Validate Connection

Click the Validate Connection button to test the settings before saving.

The validation checks:

  • Server is reachable
  • Credentials are valid
  • Folder is accessible
  • Protocol works correctly

Save

Click Save to create or update the FBL address.

Cancel

Click Cancel to discard changes and return to the list.


Processed Feedback Loops

When you click on the Complaints number in the FBL list, you see the Processed Feedback Loops page with details on feedback loops that have already been processed.

Page Features

  • Show entries dropdown to control page size
  • Search box to find specific complaints

Complaints Table

ColumnDescription
No.Row number
Contact IDAssociated contact record (clickable link to contact)
Email AddressThe complaining contact's email address
UserAdministrator who owns the contact
Campaign/TriggerThe campaign or trigger that caused the complaint (clickable link)
Complaint TimeDate and time the complaint was received
Message IDOriginal email message ID for reference
  • Click the Contact ID to view the contact record
  • Click the Campaign/Trigger link to view the associated campaign or trigger
  • Use pagination to browse through large numbers of complaints

Managing Feedback Loops

Editing an FBL Address

  1. Click Edit on an FBL address
  2. Modify settings
  3. Click Save
  4. Test connection to verify changes

Deleting an FBL Address

  1. Click Delete on an FBL address
  2. Confirm deletion

Changing Status

Toggle Status to enable or disable without deleting.


Registering with ISPs

Yahoo/AOL Complaint Feedback Loop

  1. Visit Yahoo's CFL (Complaint Feedback Loop) signup
  2. Verify domain ownership
  3. Register your FBL email address
  4. Wait for approval

Microsoft JMRP

  1. Visit Microsoft SNDS (Smart Network Data Services)
  2. Register your sending IPs
  3. Enroll in JMRP program
  4. Register your FBL email address

Other ISPs

Contact individual ISPs to inquire about their feedback loop programs.


Contact Flagging

How Complaint Processing Works

When a complaint is processed:

  1. Email address is extracted from complaint
  2. Contact is found in your lists
  3. Contact is flagged as Spammed
  4. Contact will not receive any further emails from the system

Spammed Status

FBL complaints result in:

  • Contact status changed to Spammed
  • Complaint reason recorded
  • Timestamp logged
  • All future emails to this contact are blocked
Permanent Flag

Contacts flagged as Spammed will not receive any further emails from Mumara. This protects your sender reputation and ensures compliance with ISP requirements.

Viewing Spammed Contacts

Navigate to Lists & Contacts → Suppression to see contacts flagged via FBL complaints.


Best Practices

Setup

  • Dedicated address - Use only for FBL processing
  • Register promptly - Enroll with ISPs before sending
  • Test thoroughly - Verify connection works
  • Monitor regularly - Check for processing issues

Complaint Management

  • Act immediately - Process complaints in real-time
  • Never re-add - Respect suppression permanently
  • Track trends - Monitor complaint rates
  • Investigate spikes - High complaints indicate problems

Prevention

  • Permission-based lists - Only email opted-in contacts
  • Easy unsubscribe - Prominent unsubscribe links
  • Relevant content - Send what subscribers expect
  • Proper frequency - Don't over-email

Monitoring

  • Target < 0.1% - Complaint rate below 0.1%
  • Check daily - Monitor complaint counts
  • Segment analysis - Identify problematic segments
  • Campaign review - Check complaints by campaign

Troubleshooting

Connection Failed

Possible causes:

  • Incorrect server settings
  • Firewall blocking connection
  • Wrong credentials

Solutions:

  • Verify server details
  • Check firewall rules
  • Test credentials directly

Complaints Not Processing

Possible causes:

  • FBL status is inactive
  • Cron job not running
  • Wrong folder configured

Solutions:

  • Enable FBL status
  • Check system cron
  • Verify mailbox folder

Contact Not Suppressed

Possible causes:

  • Contact not found in system
  • Email address mismatch
  • Processing error

Solutions:

  • Check if contact exists
  • Verify email format
  • Review processing logs

High Complaint Rates

Possible causes:

  • Poor list quality
  • Misleading content
  • Too frequent sending
  • Purchased lists

Solutions:

  • Clean your lists
  • Match content to expectations
  • Reduce frequency
  • Never use purchased lists

Complaint Rate Guidelines

Industry Standards

RateStatus
< 0.1%Good - healthy sender
0.1% - 0.3%Warning - needs attention
> 0.3%Critical - deliverability at risk

Calculating Complaint Rate

Complaint Rate = (Complaints / Emails Delivered) × 100

Reducing Complaints

  1. Improve targeting - Send relevant content
  2. Honor preferences - Respect frequency choices
  3. Easy opt-out - Prominent unsubscribe
  4. Set expectations - Clear signup process
  5. Sunset inactive - Remove unengaged contacts

Next Steps