TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Incoming Email Functionality

1 post · Mar 2018 – Jan 2019

What this trail covers

GitLab has evolved its incoming email functionality to support a wider range of email servers, including Microsoft Exchange and Google Groups, by adding support for catch-all email mailboxes. This enhances features like replying to notification emails, creating new issues and merge requests via email, and the Service Desk functionality. The domain for these services has been updated from @gitlab.com to @incoming.gitlab.com to prevent abuse.

All GitLab trails
  1. Microsoft Exchange & Google Groups now supported by GitLabThis post introduces support for Microsoft Exchange and Google Groups as email servers for GitLab's incoming email functionality. It addresses the previous limitation of requiring sub-addressing by adding support for catch-all email mailboxes, thereby enabling features like replying to notification emails, creating issues/merge requests via email, and Service Desk functionality for users of these email providers.
  2. GitLab inbound email issue notificationThis post details a security vulnerability where the @gitlab.com domain for inbound email creation of issues and service desk interactions could be abused. It outlines customer remediation steps to update aliases and whitelisted domains to @incoming.gitlab.com, and GitLab's remediation strategy to update all @gitlab.com addresses to @incoming.gitlab.com by April 31, 2018, to prevent abuse.