From f22524af198c0d086d3ae5a37476818de7b15d26 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= Date: Mon, 15 Feb 2021 14:54:58 -0500 Subject: [PATCH] document the recent spampd issue on rude/RT --- howto/rt.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/howto/rt.md b/howto/rt.md index f749ec15..9ab9f122 100644 --- a/howto/rt.md +++ b/howto/rt.md @@ -296,6 +296,31 @@ warnings, the user should just be re-enabled. TODO: explain how to block users otherwise. See [issue 33314](https://gitlab.torproject.org/tpo/tpa/team/-/issues/33314) for more information. +### Email delivery fails + +If no email is coming into RT, it might be one of the spam filters +that failed to start. Nagios would complain with a message like: + + Subject: ** PROBLEM Service Alert: rude/process - spampd - master is CRITICAL ** + + [...] + + Service: process - spampd - master + Host: rude + Address: 116.202.120.187 + State: CRITICAL + + Date/Time: Thu Feb 11 14:53:44 UTC 2021 + + Additional Info: + + PROCS CRITICAL: 0 processes with UID = 112 (spampd), command name spampd, PPID = 1 + +It's still unclear why this happens (see e.g. [issue 40175](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40175)), but a +workaround is to either reboot the server or restart `spampd`: + + systemctl restart spampd + # Reference ## Installation -- GitLab