As of GitLab 11.7, you can now use either Microsoft Exchange or Google Groups with your self-managed GitLab instance, configured as an email server, giving you even more options when setting up incoming email functionality. Users of GitLab.com are unaffected by this change, and already have access to features requiring incoming email, per their specific subscription.
There are several important features in GitLab that depend on users being able to receive emails from GitLab:
- Comment on issues and merge requests by replying to notification emails
- Create a new issue via email with a user-specific email address
- Create a new merge request via merge request with a user-specific email address
- Service Desk: Have your customers email in feedback/support which are converted directly into GitLab issues
Previously, these features were available to self-managed GitLab users only if your email server supported sub-addressing. Microsoft Exchange and Google Groups do not support sub-addressing. GitLab 11.7 now supports both sub-addressing and catch-all email mailboxes, enabling compatibility with these two popular options that do provide catch-all email mailboxes.
Read more about configuring incoming email in GitLab.
Cover image by mathyaskurmann on Unsplash
“GitLab incoming email now supports Microsoft Exchange and Google Groups” – Victor Wu
Click to tweet