Mailu/core/dovecot/conf/ham.script

#!/bin/bash
RSPAMD_HOST="$(getent hosts {{ ANTISPAM_ADDRESS }}|cut -d\  -f1):11334"
if [[ $? -ne 0 ]]
then
	echo "Failed to lookup {{ ANTISPAM_ADDRESS }}" >&2
	exit 1
fi

tee >(rspamc -t 3 -h $RSPAMD_HOST -P mailu learn_ham /dev/stdin||true) \
       >(rspamc -t 3 -h $RSPAMD_HOST -P mailu -f 11 fuzzy_del /dev/stdin||true) \
       >(rspamc -t 3 -h $RSPAMD_HOST -P mailu -f 13 fuzzy_add /dev/stdin||true) > /dev/null

wait
Fix rspamd-learn when moving mail from/to junk folder Before, the ham/spam scripts got the rspamd-ip/port from the environment. However, when checking the environment of these processes now, it seems cleared. Maybe the new dovecot version now clears environment? — I couldn’t find a hint. In any case, using the common mechanism of injecting the ip/port from where it’s definately known by the already-used jinja2-mechanism seems reasonably safe. 2019-09-27 20:57:15 +02:00			`#!/bin/bash`
Enable dynamic resolution of hostnames 2022-12-08 13:46:31 +02:00			`RSPAMD_HOST="$(getent hosts {{ ANTISPAM_ADDRESS }}\|cut -d\ -f1):11334"`
Ensure that we don't do multiple DNS lookups in the sieve script 2021-08-21 17:10:37 +02:00			`if [[ $? -ne 0 ]]`
			`then`
Enable dynamic resolution of hostnames 2022-12-08 13:46:31 +02:00			`echo "Failed to lookup {{ ANTISPAM_ADDRESS }}" >&2`
Ensure that we don't do multiple DNS lookups in the sieve script 2021-08-21 17:10:37 +02:00			`exit 1`
			`fi`

We also need a wait now that we capture stdin 2023-08-16 10:44:10 +02:00			`tee >(rspamc -t 3 -h $RSPAMD_HOST -P mailu learn_ham /dev/stdin\|\|true) \`
Prevent rspamc zombies, ensure that triggering learn-spam works 2023-08-15 10:14:27 +02:00			`>(rspamc -t 3 -h $RSPAMD_HOST -P mailu -f 11 fuzzy_del /dev/stdin\|\|true) \`
As per review 2023-08-15 19:32:41 +02:00			`>(rspamc -t 3 -h $RSPAMD_HOST -P mailu -f 13 fuzzy_add /dev/stdin\|\|true) > /dev/null`
We also need a wait now that we capture stdin 2023-08-16 10:44:10 +02:00
			`wait`