Disable all notification emails

For some reason, I can't edit this issue, but I do want to say that we want to keep account verification emails and other account maintenance emails, which is why we just haven't removed the email server.

@icco Thanks for the proposal.

It's definitely a feature that would be awesome.

It would also be useful to be able to disable all outgoing emails when debugging or experimenting with something in GitLab. Obviously this should be an admin-only function.

Definitely would be helpful to have.

@vadacom.benjamin-rood Outgoing emails from GitLab can be disabled completely:

https://gitlab.com/gitlab-org/gitlab-ce/blob/91a3a4b526214f4174f4f12de23dfb5baf033211/config/gitlab.yml.example#L67

This issue refers to only notification email disablement, excluding account specific emails like confirmation and password resets etc. Currently, it's all or nothing.

This would be very useful, though I would want two variations also available:

Disable notifications per-group
Mask the content -- eg, send the email, but only say something like "An issue was filed at URL"

I pushed gitlab-ce!19686, it works locally in my development environment. It does what I need -- namely, the ability to disable notifications per-group or per-project. After some contemplating, I decided against masking the email content as that didn't really fit into my requirements.

Thinking about it, it would probably be fairly easy to extend my MR to work globally too. However, I've already spent more time on this than I was hoping to spend.

FWIW, we've been using gitlab-ce!19686 on two gitlab 10.x installations since the beginning of July, and it has worked out great for us. Just need someone to review the MR and provide guidance for writing tests, then hopefully it can be introduced into mainline Gitlab.

@victorwu What do you think about this one? A Merge Request has been prepared

@smcgivern @jeremy_ : What do you think about this feature?

What do you think about this feature?

Comment moved to https://gitlab.com/gitlab-org/gitlab-ce/issues/50020

Let's not get off from the original request: disable email except account related ones (password reset, account verification, etc.). I think that satisfies @jeremy_'s UX requirements (clear radio silence). Current email flag disables password reset, etc., so isn't a solution.

Whoops, I thought I was posting this in the MR that's currently out (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/19686) that does what I described.

Let's not get off from the original request: disable email except account related ones (password reset, account verification, etc.). I think that satisfies @jeremy_'s UX requirements (clear radio silence). Current email flag disables password reset, etc., so isn't a solution.

I agree. My comments were directed at that MR, which opts for selective disabling of notifications on a project/group basis. In my view, we shouldn't do this.

Sorry for the confusion @jeremy_ . I created a separate issue that matches the MR. Can you please paste your comment on that new issue?

It is here; https://gitlab.com/gitlab-org/gitlab-ce/issues/50020

Thanks a million for the new issue. My fault for not noticing this issue and the MR were a bit different to one another

Any update for this?

added devopsplan label

added [deprecated] Accepting merge requests label

added groupproject management label

removed [deprecated] Accepting merge requests label

added auto updated potential proposal labels

Large Premium customer is interested in this feature. https://gitlab.zendesk.com/agent/tickets/143908 (GitLab internal only)

added customer label

added customer+ label

mentioned in issue #197801 (closed)

mentioned in issue #198984 (closed)

mentioned in issue #201640 (closed)

mentioned in issue #212102 (closed)

mentioned in issue #212794 (closed)

mentioned in issue #212807 (closed)

mentioned in issue #213483 (closed)

mentioned in issue #214175 (closed)

mentioned in issue #214945 (closed)

mentioned in issue #215811 (closed)

mentioned in issue #216406 (closed)

A large enterprise customer (Premium) is interested in this feature https://gitlab.my.salesforce.com/0016100000gooIO

would be highly beneficial to us in our HA GitLab environment, particularly when setting up a new environment, such as restoring a backup, or setting up Geo. We can get around this by disabled SMTP in the omnibus config across all of our application nodes, but it would be more convenient to be able to control this via the UI or an API call.