mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.

---
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
  ------- --------------