I have two non-production Bitbucket servers, used for testing and development, and I do not want them to ever send email (e.g. when pull requests are merged). Does setting the *atlassian.mail.senddisabled
* JVM argument at startup disable outgoing email for Bitbucket, like it does for JIRA?
Hi @Kent Rogers,
While the atlassian.mail.senddisabled configuration option is valid for Jira, it does not apply to Bitbucket Server.
We have an open feature request on this topic here:
- BSERV-8620 - As an admin, I want to easily disable mail notifications with a configuration property
In one of the comments, Roger suggested this workaround, which applies also to a staging environment
For disaster recovery purposes, a workaround I would like to suggest is to change the firewall settings for the DR instance to block outbound email.
Another alternative would be to remove the email server on the test server by using this REST API endpoint:
DELETE /rest/api/1.0/admin/mail-server
Cheers,
Caterina - Atlassian
Hi @Caterina Curti,
Thank you for the pointer to the BSERV issue. The second case listed there, "Mirroring a production system to a development/staging server", is exactly our situation. Our DEV/UAT servers get refreshed from production on a regular basis, and while I can remove the email server, I would rather not have to do that every time there is a refresh, and there is a risk of it not happening.
I have added my vote to that issue and am now watching it. Since it has already been implemented in JIRA & Confluence, I'm hoping it is not that difficult to do in Bitbucket and will be considered in the relatively near future.
-Kent
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Kent!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.