view mod_block_outgoing/README.md @ 6319:04c3273cb81f

mod_auth_cyrus: Add empty 'profile' table to SASL handler objects This is for compatibility with Prosody's built-in util.sasl objects. A SASL profile table usually includes methods supported by the backend, which can be used by SASL mechanism handlers to perform operations (such as testing the password). It also optionally contains a 'cb' field with channel binding method handlers. The Cyrus backend doesn't support channel binding, and doesn't have the same concept of auth backend methods (it handles all that internally, and Prosody has no insight or control over it). Thus, we create an empty profile which informs Prosody that the SASL handler does not support any of the auth or channel binding methods. Some features will not work, but they didn't work anyway. This just makes it explicit. This fixes a traceback in mod_sasl2_fast, which expected SASL handlers to always contain a 'profile' field.
author Matthew Wild <mwild1@gmail.com>
date Thu, 04 Sep 2025 10:14:46 +0100
parents fe081789f7b5
children
line wrap: on
line source

---
summary: 'Block outgoing stanzas from users'
...

Introduction
============

This module blocks all outgoing stanzas from a list of users.

Using
=====

Add mod_block_outgoing to the enabled modules in your config file:
``` {.lua}
modules_enabled = {
	-- ...
		"block_outgoing",
	-- ...
}
```

Either in a section for a certain host or the global section define which users and what stanzas to block:
``` {.lua}
block_outgoing_users = { "romeo@example.com", "juliet@example.com" }
block_outgoing_stanzas = { "message", "iq", "presence" }
```

block_outgoing_stanzas defaults to "message" if not specified.

Compatibility
=============

  ------- --------------
  trunk   Doesn't work (uses is_admin)
  0.12    Works
  0.11    Works
  ------- --------------