• 25
    • 1
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      The mail error queue is currently useless.

      • You have no indication what the error is
      • All you can do is "resend all" or "delete all"

      We need to work on the same principles as an MTA.

      • If an error is permanent, give up and log the error somewhere.
      • If an error is transient, put it on a queue to resend after a few hours.
      • If a transient error keeps happening for a certain amount of time, give up and log the error somewhere.

      Also useful would be:

      • Keep track of users whose mail fails repeatedly, and stop sending them anything. Flag the account, and have a big note on their profile page saying "Notifications are currently disabled for this account due to repeated mail delivery failures. Please turn notifications back on on your notifications preferences page."
      • Mail fails with 'was not a permissible recipient' error should go to Error Queue
      • Notification email queue should persist across restarts of Confluence (CONF-3556)

            [CONFSERVER-3231] Fix the mail error queue

            This issue causes the confluence log file to fill. Please address fixing this problem.

            Mary Washburn added a comment - This issue causes the confluence log file to fill. Please address fixing this problem.

            To make the View Mail Queue > Error Queue more useable, I suggest adding a 'To' address field so you know who it is being sent to. And if it is a bad e-mail address, the option to delete the selected mail would also be useful.

            Christopher Taleck added a comment - To make the View Mail Queue > Error Queue more useable, I suggest adding a 'To' address field so you know who it is being sent to. And if it is a bad e-mail address, the option to delete the selected mail would also be useful.

            Don Willis added a comment - - edited

            This issue can still lead to an OutOfMemoryError (as described by CONF-3333). It just requires more items in the error queue now. I measure <= 280 messages taking up 30 MB. That's still pretty bad. This queue needs to be persisted in the Database as suggested in CONF-3556.

            Don Willis added a comment - - edited This issue can still lead to an OutOfMemoryError (as described by CONF-3333 ). It just requires more items in the error queue now. I measure <= 280 messages taking up 30 MB. That's still pretty bad. This queue needs to be persisted in the Database as suggested in CONF-3556 .

            Sulka Haro added a comment -

            While working at this, could you make this happen to Jira too? The exact same issues affect Jira.

            Sulka Haro added a comment - While working at this, could you make this happen to Jira too? The exact same issues affect Jira.

            We need to consider persisting the error queue so that valid emails are not lost during a restart.

            Daniel Ostermeier added a comment - We need to consider persisting the error queue so that valid emails are not lost during a restart.

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              57 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated: