Check the From header for inbound mail
- Lenguaje dominante
- Go
- Estrellas
- 6.1k
- Forks
- 327
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
# Use case
I have received spam email whose domain of MAIL FROM is valid and the EHLO host is also allowed by the SPF.
However, the From header in the body is not match the MAIL FROM command.
This is a clear clue of spam. We need to check this situation. I have read the doc of check.authorize_sender,
it can be only used for checking the From header for outbound mail.
# Your idea for a solution
One solution is to add an additional new check for the FROM header, and implement the check logic in the bodyCheck callback.
However, this solution need to add certain configure in the configure file.
I suggest to write a fix check function in the mgspipeline or check_runner and make this as default check so that there is no need to add new configuration.
- [x] I'm willing to help with the implementation
Guía de contribución
Línea de trabajo
Comienza leyendo la documentación de check.authorize_sender y localiza los entry points bodyCheck callback, mgspipeline y check_runner mencionados en el issue. Determina dónde se pueden comparar MAIL FROM y From headers entrantes y, a continuación, verifica que el check predeterminado previsto detecte la discrepancia sin configuración adicional.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go
- Área
- authentication, security
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100