mirror of
https://github.com/Mailu/Mailu.git
synced 2024-12-14 10:53:30 +02:00
9c956a04ca
1183: Fix rspamd-learn when moving mail from/to junk folder r=mergify[bot] a=Nebukadneza 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. ## What type of PR? bug-fix ## What does this PR do? Instead of relying on dovecot passing our environment cleanly to sieve-called scripts, this explicitly injects the antispam ip/port into the spam/ham scripts used when moving files from/to the spam-folder. This required some management of the files, such as setting proper permissions after the jinja-run. ### Related issue(s) fixes #1177 ## Prerequistes - [x] In case of feature or enhancement: documentation updated accordingly - [x] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file. Co-authored-by: Dario Ernst <dario@kanojo.de> Co-authored-by: Dario Ernst <dario.ernst@rommelag.com> |
||
|---|---|---|
| .. | ||
| admin | ||
| dovecot | ||
| nginx | ||
| none | ||
| postfix | ||