diff --git a/roles/custom/matrix-synapse/defaults/main.yml b/roles/custom/matrix-synapse/defaults/main.yml
index a611e862d..8d0cd61f8 100644
--- a/roles/custom/matrix-synapse/defaults/main.yml
+++ b/roles/custom/matrix-synapse/defaults/main.yml
@@ -1426,12 +1426,12 @@ matrix_synapse_ext_synapse_http_antispam_config_authorization: ''
 # This controls what callbacks are activated. This list is fully dependent on what consumer is in play.
 # And what capabilities said consumer should or shouldn't have. There are also performance implications
 # to these choices.
-matrix_synapse_ext_synapse_http_antispam_config_enabled_callbacks: ''
+matrix_synapse_ext_synapse_http_antispam_config_enabled_callbacks_yaml: ''
 # Controls if a loss of connectivity to the consumer results in fail open or closed.
 # As in if failure results in events getting flagged automatically as spam or not.
-matrix_synapse_ext_synapse_http_antispam_config_fail_open: ''
+matrix_synapse_ext_synapse_http_antispam_config_fail_open_yaml: ''
 # Controls if the checking is blocking or not. This allows the homeserver to skip waiting for a consumer response.
-matrix_synapse_ext_synapse_http_antispam_config_async: ''
+matrix_synapse_ext_synapse_http_antispam_config_async_yaml: ''
 # Actual configuration passed to the synapse-http-antispam module
 matrix_synapse_ext_synapse_http_antispam_config: "{{ matrix_synapse_ext_synapse_http_antispam_config_yaml | from_yaml }}"
 matrix_synapse_ext_synapse_http_antispam_config_yaml: |