Mailgun Suppression Scans

#Overview

The central Mailgun page shows addresses affected by a bounce or complaint and recent failed messages that may be safe to resend. It also helps staff see whether those addresses are used by tenant forms or sent emails.

#Managing Suppressions

Open the central Mailgun page to see the latest cached scan. Three summary cards show entries pending deletion, form notification matches, and resendable failures.

Click a summary card to filter the table to exactly the rows it counts. Pending Deletion shows every pending row, Form Notification Matches shows addresses used by tenant form notifications, and Resendable Failures shows all recent failures that may be safe to resend.

The initial table combines bounces, complaints, and resendable failures. The Type badge and Details column distinguish them without requiring a filter. Set Type to Failure to show the additional recipient domain, subject, failure reason, SMTP response, and duplicate-event columns. Failures cover the previous seven days. This page does not resend email.

Rows pending deletion are shown by default. Select Delete to remove a row from the working list. The confirmation explains that this does not call Mailgun's delete API and does not alter the suppression in Mailgun. Set Status to Deleted or All to see removed rows again.

#Running a Scan

Use Scan Mailgun to start a fresh scan. The page shows scan progress while the job is running and continues to show the previous completed scan until the new scan finishes. If Mailgun failures cannot be refreshed or the job stops unexpectedly, the page shows the scan error instead of presenting stale data as a normal successful scan.

#Scheduled Scans

Use Schedule settings from the suppressions page to enable automatic scans. The scheduler checks every ten minutes and runs a scan only when the selected interval is due.

Alert emails are sent only to addresses configured on the schedule settings page. Each recipient is alerted once for every matching row that is pending deletion, even if a manual scan found the row before the scheduled scan. The same row is not emailed to that recipient again unless its identity or tenant impact changes. If no alert emails are configured, scheduled scans can still run but no alert is sent.

Use Alert address sources to choose form notification recipients, tenant sent-email recipients, or both. The default is form notification recipients so end-customer addresses found only in sent-email history do not trigger alerts unless that source is explicitly enabled.

Use Alert event types to choose bounces, complaints, and resendable failures. All three are enabled by default. The email reports a separate count for each type and links back to the matching filtered table when one source or one event type is selected.