summaryrefslogtreecommitdiff
path: root/changelog.d/retire_mrfs.remove
diff options
context:
space:
mode:
authorMark Felder <feld@feld.me>2025-02-28 16:40:38 -0800
committerMark Felder <feld@feld.me>2025-02-28 16:43:28 -0800
commit2c9d071aadde88e8ab615be6654e237ae01decb7 (patch)
treec189e9325782f602fddd499a2ef0fe108dc7b17f /changelog.d/retire_mrfs.remove
parent63663ac88bae834621417a1084e507831a44e7e2 (diff)
downloadpleroma-2c9d071aadde88e8ab615be6654e237ae01decb7.tar.gz
pleroma-2c9d071aadde88e8ab615be6654e237ae01decb7.zip
Retire MRFs DNSRBL, FODirectReply, and QuietReply
DNSRBL was a neat experiment which should live out of tree. It works and could be used to coordinate rules across different servers, but Simple Policy will always be better FODirectReply and QuietReply have reliability issues as implemented in an MRF. If we want to expose this functionality to admins it should be a setting that overrides the chosen scope during CommonAPI.post instead of trying to rewrite the recipients with an MRF.
Diffstat (limited to 'changelog.d/retire_mrfs.remove')
-rw-r--r--changelog.d/retire_mrfs.remove1
1 files changed, 1 insertions, 0 deletions
diff --git a/changelog.d/retire_mrfs.remove b/changelog.d/retire_mrfs.remove
new file mode 100644
index 000000000..2637f376a
--- /dev/null
+++ b/changelog.d/retire_mrfs.remove
@@ -0,0 +1 @@
+Retire MRFs DNSRBL, FODirectReply, and QuietReply