Skip to content

WIP: Mailings: Add a Review Bounces screen#35132

Draft
mlutfy wants to merge 1 commit intocivicrm:masterfrom
mlutfy:mailingBounces
Draft

WIP: Mailings: Add a Review Bounces screen#35132
mlutfy wants to merge 1 commit intocivicrm:masterfrom
mlutfy:mailingBounces

Conversation

@mlutfy
Copy link
Member

@mlutfy mlutfy commented Mar 17, 2026

Overview

Admins should be warned when there is a high bounce rate, and they should be encouraged to review their bounces so that they can better deal with the situation.

This PR adds a "Review Bounces" menu under Mailings, with a FormBuilder-based screen.

Before

Admins might notice a high bounce rate if they calculate it manually while looking at a specific mailing, but they won't be alerted about it. They might also not know about the Reports > CiviMail > Bounces (which is nice, but messy by default, not sane default filters).

After

image

(todo: update screenshot: I added the contact name)

image

TODO

  • Form/Search to view recent bounces
  • Fix navigation menu item
  • See if we can use the same SearchKit/FormBuilder for the "view single email bounces", "view all bounces" and "view a specific mailing bounces". And do the same for unsubscribes and opt-outs.
  • System Check for high bounce rate
  • SearchKit action to remove "on hold" (because sometimes it bounced for the wrong reason)

Wishlist:

  • Form/Search should limit to "last 10 days" or something like that, instead of listing all bounces
  • Display the email? I'm not sure if that will kill performance. Makes it easier to spot that the problem is, for example, with Microsoft, or filter by email domain.

@civibot
Copy link

civibot bot commented Mar 17, 2026

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers...

➡️ Online demo of this PR 🔗

@civibot civibot bot added the master label Mar 17, 2026
@mlutfy mlutfy force-pushed the mailingBounces branch 2 times, most recently from e48b31d to cc725a8 Compare March 17, 2026 21:19
@mlutfy mlutfy marked this pull request as draft March 18, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant