Email notifications don't get sent on category change for mailing list mode users

AI-generated summary

Users in mailing list mode are not receiving email notifications when a topic is moved from a secure category (e.g., Staff) to a public one, despite gaining access. This impacts workflows where topics are drafted privately before being published publicly, causing power users to miss important announcements. wesochuck documented the issue and confirmed it persists in version 3.3.0.beta2 wesochuck. RGJ identified the root cause — the system never triggers notifications for this specific scenario — and proposed a fix by calling :notify_mailing_list_subscribers within the NotifyCategoryChange job, which was verified to work. The Discourse team confirmed they would accept a PR for this fix lindsey. jyuvaraj03 submitted a PR, which was subsequently merged by zogstrip. The bug has been resolved and is tagged as ‘fixed’.

Repo steps:

  1. Set a user account to mailing list mode.
  2. Post a topic in a secure category that the user doesn’t have access to (e.g. Staff)
  3. Change the category to of the topic to a public category that the user does have access to
  4. The mailing list mode user will never get an email notification of the topic

This affects us on a regular basis because we typically jointly compose topics in a DRAFT mode in our staff category before pushing them out to our users. We also have several power users in our forum that use mailing list mode to make sure they “don’t miss anything” and of course, in this case, they end up missing some of our most public announcements.

More background:

Continuing the discussion from Mailing list mode user not getting emails and not appearing in skipped_email_logs:

1 Like

Just updating that I’ve confirmed this is still an issue in version: 3.3.0.beta2

We have found the issue. This case is simply never accounted for.

A solution is to call :notify_mailing_list_subscribers from the NotifyCategoryChange job. I have just verified that this is working.

Team, would you accept a PR for this or is this plugin territory?

3 Likes

Sure, we’d be happy to review a PR for this update. Thanks!

2 Likes

I have raised a PR for this fix!

3 Likes

Thanks @RGJ / @jyuvaraj03 - I’ve merged the PR :white_check_mark:

5 Likes

This topic was automatically closed after 2 days. New replies are no longer allowed.