8 years now... we trying to troubleshoot email issues.... sigh.

Wow, 5 years ago and counting...

Even if we can't get a screen in the UI, at least let us change the log level for atlassian-bitbucket-mail.log so we can see there what's happening. Or maybe I just need to find that setting somewhere?

I would also like some visibility into this main queue. When I send a support request from Bitbucket Server Troubleshooting and Support Tools page, I get this:

Support request submitted!

Your message regarding "blah, blah, blah" has been added to the mail queue.

Opening to gauge further interest.

Hello Brent,

Thanks for this reply.

About why i rather use an in-app monitoring is simple for my case : i work for a french bank where segregation of duty and security policies are very strict (we are still a long way from a real DevOps bank). 

So, very simple : as admin i can access application but i have a very limited access to the host itself. Impossible to install dedicated tools or just activate JMX ports. (at least without filling endless excel forms to IT Security team).

I am aware it's a limitation on our side and, in the whole IT mondial context, we should move to an another paradigm but i guess you have other clients with the same issues.

Hope this answer was clear

samy.lerari - I'm very sorry but it appears I jumped the gun and was a bit confused about the work in progress. As part of BSERV-9502, we added more logging around the mail system but that didn't get merged in time for 4.14. In Bitbucket Server 5.0, you will be able to monitor the mail system with JMX. Unfortunately, I don't believe that work included a user-visible screen in the Support Tools admin section so I've re-opened this issue.

We're still looking for some feedback on why you'd prefer in-app monitoring over centralized monitoring on your SMTP infrastructure. Roger asked this above:

Would you mind elaborating on your use case here? We typically recommend that production instances of any significant size use a local SMTP relay to handle queueing etc, but I'm open to considering an improvement once I better understand the context.

If you or venkat.patchigolla1 can give us some more detail, that'd help us priioritize this issue.

Hello Brent,

I looked into information available in Support Tools admin section on a running and working 4.14.3 instance without finding any information about mail queue size.

Are you sure it's available in support tools ?

Thanks

For Bitbucket Server 4.14 (the next version we'll release), you can view the mail queue size in the Support Tools Plugin and as a JMX metric.

Hi venkat.patchigolla1, would you mind elaborating on your use case here? We typically recommend that production instances of any significant size use a local SMTP relay to handle queueing etc, but I'm open to considering an improvement once I better understand the context.