Skip to content
CMS Max Documentation

Mailgun Suppression Scans

Manage Mailgun bounces, complaints, and resendable failures across tenant sites

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 needing review, form notification matches, and resendable failures.

Click a summary card to filter the table to exactly the rows it counts. Needs Review shows every unreviewed 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, with addresses used by form notifications listed first and the remaining addresses ordered newest first. The Tenant Usage column names each matched tenant and summarizes the number of form notifications and sent emails. Select that summary to load the matching forms and emails in a modal; long histories show the first 100 matches. Tenant unavailable means usage was found but the tenant label is no longer available in the scan results. Use the Linked via multi-select to show form notifications, sent emails, unlinked addresses, or any combination of them. The Type badge distinguishes events without requiring a filter. Select View details on a row to see its full Mailgun message and, for failures, the recipient domain, subject, failure reason, SMTP response, and related event count. The table search can also find rows by these details even though they appear only in the modal. Failures cover the previous seven days. A fresh scan removes a failure when Mailgun confirms a later successful delivery of the same message to the same recipient. Temporary failures may still be awaiting an automatic retry; a listed failure does not prove the message was never delivered. This page does not resend email.

Rows needing review are shown by default. Select Mark reviewed to remove a row from the working list without altering the suppression in Mailgun. Set Status to Reviewed or All to see reviewed 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. If only delivery verification is incomplete, fresh failures are still shown with a warning that some may already have been delivered. Confirmed deliveries are removed even if another delivery lookup fails.

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. After a scheduled scan, each recipient gets at most one alert a day. The alert lists every tenant site with an address that needs review, and under each address the site's forms and sent emails that use it, the event type, and Mailgun's reason. Long alerts list the first 100 entries and link to the page for the rest. No alert is sent when nothing needs review, when the scan fails, or when no alert emails are configured. Rows marked reviewed drop out of the next alert.

Use Send test email on the schedule settings page to send the alert to the saved alert emails right away. It uses the latest scan, says when nothing needs review, and does not replace that day's scheduled alert. Save any changes to the alert emails or filters before sending.

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.