kedzierski1051458675, please see the docs

Notifications are immediate for some actions such as mentions, this cannot be changed. For all others they go into the batch window, which by default is 10 minutes.

n.milosavljevic55090231, this feature was introduced in 5.10. If you are getting no emails then the cron string could be wrong (the default is 0 0/10 * 1/1 * ? *) or maybe you dont have an email server configured. You can change the 10 to a higher number for less frequent emails.

Note, this is a window, therefore not x minutes from publishing a change, it is a fixed schedule.

@Adam Barnes

Thank you for releasing this change! Could you, please, share how to use batched email notifications instead of immediate ones on Confluence Server 6.0.5? I see that there is a job called "Send Batched Notifications" listed at URL path admin/scheduledjobs/viewscheduledjobs.action, but I can't see any means of disabling immediate notifications globally, so that only these batched remain.

Thank you!

@Adam Barnes

Previously mentioned:

...receive immediate emails for important notifications (like mentions and new pages), but when lots of changes are being made at the same time, you'll only receive a single email with all the changes (within a short window, usually 10 minutes).

How should the "important notifications" behave on the Confluence server?

Also I have configured the the "Send Batched Notifications" scheduled job to execute at the certain time, for example 10 minutes from now by defining the configuration like so "0 45 10 * * ?" but no email has arrived. So in term I believe that the feature does not work.

n.milosavljevic55090231, what behaviour are you referring to.

@Adam Barnes

Will the Confluence server get the same behavior soon? 

Thanks for this. It would be nice if in the future you could make the window time interval a user-settable thing so users can set the granularity of these mini-digests for changes to watched pages.

Glad you are picking this up and rolling out changes finally! Do you have any screenshots for example of the "combined" email that will be send out after that time-interval of 10 minutes?

The real thing we also desperately need is improved CONF-5566 Daily or weekly notifications with possibly chance for the user to select which spaces he is interested in. Can you plan that next?

We are pleased to announce that this feature has now been released in Confluence Cloud and 5.10. Thank you for your all your input into this suggestion.
Now, you'll receive immediate emails for important notifications (like mentions and new pages), but when lots of changes are being made at the same time, you'll only receive a single email with all the changes (within a short window, usually 10 minutes).

For Confluence Server, System Administrators can configure the duration of the batch window (via a scheduled job). Increase the time for fewer emails or reduce the time if more immediate notifications are essential in your site.

We've had this same problem. For a tool that claims to reduce email, Confluence makes it far too easy (especially for novice users) to have their inboxes flooded with email from Atlassian. One of the first pages I point new users to is our internal guide on how to turn off Confluence spam! Personally, I have stopped watching any pages in favor of the daily digest. Not ideal, but at least it's manageable.

We started using the feedback feature today over that of office 365. My inbox has exploded. I now have a couple choices. Create a rule that dumps all the stuff in a folder, which will get ignored. Stop watching pages, which will also get it get ignored, or waste more of my time each day managing the hundreds of emails coming at me. It wouldn't be so bad if the emails were grouped as conversations in outlook, but they are not.

With out aggregation this thing is wasting enough time that it's no longer a benefit.