Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

chore: default to Rspamd from v17.0.0

Abierto
  • ¿Algo no está bien?
#4,364 12 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@georglauterbach ya está trabajando en esto.

Desde el 13/8/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

area/features area/security meta/help wanted service/security/amavis service/security/dkim-dmarc-spf service/security/postgrey service/security/rspamd service/security/spamassassin stale-bot/ignore
Description

I cite reasoning for preferring Rspamd as a maintainer here.

I am interested in feedback from anyone that prefers any of the existing suite of services that Rspamd replaces, which I'm now considering as legacy services in DMS (they are not pleasant to maintain/troubleshoot and have cost a fair amount of time over the years, unresolved issues aside):

Legacy services:

Links are to their associated setup script in DMS, but most have config/docs/tests elsewhere in the project and many associated past issues in the project.

An example of an issue I recently noticed was a difference in behaviour with SA scanning from DMS v14 (released in June 2024, upgraded to Debian 12 (June 2023) base image + SpamAssassin 4.0 (Dec 2022)), these sorts of issues require a fair amount of time to investigate and ideally resolve / document the cause when we lack maintenance expertise for these services.

The legacy set of services will remain for the time being as a fallback / alternative option. We've had Rspamd offered since DMS v12 (April 2023) and improved our support and docs a fair amount since then.

Eventually it would be preferrable to unload the burden of maintaining support for the legacy services. Thus if any users could share any concerns/experiences for why they might prefer any of the legacy services over Rspamd that'd be appreciated. Most alternatives to DMS already use Rspamd instead of our equivalent legacy set of services to my knowledge.

DMS v15 docs for Rspamd have had an initial revision with the intention of being easier to grok for users wanting to switch early. There will likely be some breaking changes for Rspamd in DMS v17, I may also try to push for upstream Rspamd to publish packages to their deb repo we use so that we can actually pin Rspamd releases for more deterministic image builds.

Lenguaje dominante
Shell
Estrellas
19.7k
Forks
2.1k
Merge medio
22 h 39 min
PR fusionados (30 d)
8

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de docker-mailserver/docker-mailserver

Todos los issues de docker-mailserver/docker-mailserver

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.