this question is slightly related to the Confluence Archiving Plugin, but the same problem can occur with any type of Confluence email sending, so in that sense it is fairly generic.
the problem: the Archiving Plugin sends emails when detecting outdated content, to all persons who may potentially update or delete it (authors and admins). in popular spaces, it can be a large group of users, which means a lot of emails to be sent out within a short time period.
our users complain that their servers are "flooded" with the amount of emails, and they sometimes loose important notification mails.
i understand that this is basically an infrastructrual problem, well outside the scope of Confluence, but looking for a workaround.
question: is it possible to fine-tune "the batch size" and "sending frequency" of the Confluence mail queue? for example, can I configure it like this: even if you have 73 mails to send, send only 20 at a time and wait 15 seconds between two batches?
I don't think the number of mails per batch can be easily configured for now. It might require code changes. I might be wrong though. However, the scheduled job (i.e. mailQueueFlushJob) frequency is configurable. The linked page would describe how to configure it for Confluence 3.5.x or higher. If you're using a lower version, you will need to modify schedulingSubsystemContext.xml as described here.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
To anyone who doubts that Atlassians are a little too obsessed with collaboration, and tools related thereto, let me describe a recent discussion we had (which took place on our internal Confluence, ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs