Issue Summary

When the mail server is configured in Bitbucket, it sends out all stored notifications accumulated since Bitbucket was initially set up.

This is reproducible on Data Center: yes

Steps to Reproduce

• Set up a new Bitbucket instance.
• Create a project, along with a repository, and initiate a pull request between two branches of that repository.
• Mention a user with a message within the pull request comment.
• Wait for a while, then go to Settings > Mail server to configure the mail server details.
• Once the mail server is configured, Bitbucket immediately sends a notification to the tagged user.

Expected Results

Bitbucket should only send notifications for events that occur after the mail server is integrated

Actual Results

Once the mail server is configured, it sends out all stored notifications accumulated since Bitbucket was initially set up. However, It should not dispatch old notifications, as the mail server might be configured years later, which would send large volume of outdated notification to the users.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available