<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=590796) </details> <!--IssueSummary end--> In GitLab 19.0, we are removing [Spamcheck](https://docs.gitlab.com/administration/reporting/spamcheck/) from the Linux package and GitLab Helm chart. Spamcheck is a service to combat spam on public-facing GitLab instances. By its nature, this feature is primarily relevant to large public instances, which represents an edge case in our customer base. Given the low adoption and the availability of standalone deployment options, we are removing Spamcheck from the Linux package and GitLab Helm chart. Customers not using Spamcheck will not be impacted by this change. The removal will reduce package size and dependency footprint (and thus security) for the majority of customers. If you currently use the bundled Spamcheck, you can deploy it separately by using [Docker](https://gitlab.com/gitlab-org/gl-security/security-engineering/security-automation/spam/spamcheck). No data migration is required. Configuration guidance is available in the linked documentation. Please share your feedback, concerns, or use cases related to this change.