Issue Summary

When the mail queue or mail error queue contains entries, the title of each queue tab indicates the number of entries within their section. However, clicking on either "Mail Queue" or "Error Queue" shows no details related to those entries.

This is related to CONFSERVER-94502, but it specifically affects mail notifications originating from the Send Batched Notifications scheduled job.

• Send Batched Notifications (affected)
• Email Daily Reports (fixed in CONFSERVER-94502)
• Send Recommended Updates Email (fixed in CONFSERVER-94502)

Steps to Reproduce

1. Configure a mail server with Confluence
2. Use a proper email address for the admin user profile
3. Create a new page using admin user login and ensure the admin is watching the page (which will be by default).
4. Perform some edits on the page through a different user.
5. Head to the Scheduled Jobs administration page and run the Send Batched Notifications scheduled job.
6. Ensure the admin receives the notification.
7. Now edit SMTP server details and change the port to a wrong port and save the changes. This is to ensure that mail notification fails while Confluence tries to send it.
8. Perform some edits again on the page through a different user.
9. Head to the Scheduled Jobs administration page and run the Send Batched Notifications scheduled job.

Expected Results

Mail doesn't triggers and gets stuck in Mail queue showing the entries.

Actual Results

Mail doesn't triggers and gets stuck in Mail queue showing only the number.

Now clicking on Flush Mail Queue shows the same number on the Error Queue.

 

Additional Information

Despite this bug report share the same behaviour with CONFSERVER-94502, but the reported "Daily Update" and "Recommended Updates" in CONFSERVER-94502 has indeed been fixed in the respective versions:

This is taken from Confluence 9.2.3 where the failed entries reported in CONFSERVER-94502 are showing in the UI correctly.

Workaround

We get exception if there is an error while sending notifications to particular user_key in atlassian-confluence-outgoing-mail.log which also shows the cause for failure but this is not user friendly at the moment.