Complaint FBLs

• Table of Contents
• Is feedback loop notification processing supported?

Is feedback loop notification processing supported?

Yes.

There are two kinds of Spam Complaint Processors, depending on if you are using the Normal or Lite Bounce Processor.

Normal Spam Complaint Processor:

This is used when you are using the Normal/Heavy Bounce Processor, where GreenArrow rewrites the RFC5321.MailFrom address of each message to contain a custom Variable Envelope Return Path (VERP). GreenArrow also adds a header to each email which is used when processing incoming spam complaint notifications.

The Spam Complaint Processor is very similar to the Bounce Processor mechanism, with the obvious difference being that it is triggered by a user complaint instead of a delivery failure.

When you have Feedback Loop enrollments configured to deliver complaints back to GreenArrow’s special Spam Complaint Mailbox (documented here and here), GreenArrow will receive and automatically process the spam complaint, and can send a notification about the spam complaint via the Event Notification System.

You will receive a scomp event.

Lite Spam Complaint Processor:

This is used when you are using the Lite Bounce Processor, where the RFC5321.MailFrom address is not overwritten by GreenArrow. You create your own bounce address for each message, encoding whatever information in the email address that you want.

The Lite Spam Complaint Processor is documented on the Lite Bounce Processor page.

You define incoming email addresses for spam complaints using the lite_bounce_processor_address configuration directive.

Additionally, you add whatever headers you want to encode information for spam complaint processing, and GreenArrow will return those headers to you. You let GreenArrow know which headers these are with the lite_fbl_processor_headers configuration directive.

You will receive a scomp_lite event.