Suppressions and Unsubscribe

Suppression is a non-optional send-time control. When an address is suppressed, RSender skips it across campaigns and automation flows.

Suppression categories

• Hard bounce: the destination reported a permanent delivery failure.
• Soft bounce: the address is excluded under the configured handling policy after temporary failures.
• Complaint: a recipient or provider reported unwanted mail.
• Unsubscribe: the recipient requested that eligible email stop.
• Manual: an operator added an exclusion for a documented reason.

The category and reason help explain why a record cannot receive mail.

Add or import suppressions

1. Open Suppressions.
2. Choose manual add or file import.
3. Enter normalized email addresses.
4. Select the correct category.
5. Add a concise reason when available.
6. Confirm the imported or created count.

Check imports for wrong columns or malformed values before confirming.

Unsubscribe paths

RSender can use a configured unsubscribe URL or mail-based source and can support a hosted unsubscribe service when the entitlement is active. Configure the visible link in templates and enable the supported List-Unsubscribe behavior in compliance settings.

Test:

• visible link rendering;
• one-click or mail behavior where configured;
• creation of the suppression entry;
• exclusion from a later campaign and automation entry;
• hosted-service health when applicable.

Removing a suppression

Removal should be exceptional. Confirm:

1. renewed permission is documented;
2. the original bounce, complaint, or unsubscribe reason is understood;
3. organizational policy permits restoration;
4. the action is attributable in the audit trail.

Restoring a contact’s subscription state is not enough if a separate suppression still exists.

Incident handling

If suppression or unsubscribe processing is unavailable, pause affected marketing sending. Preserve logs, record the time window, reconcile delayed events, and verify exclusion behavior before resuming.

Hosted tracking and unsubscribe events are synchronized to the desktop application when those services are enabled. Network delay can affect how quickly remote events appear locally.

Next: review deliverability and reports.