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.

# This is a simple ruleset to block all traffic from servers
# on the JabberSPAM blocklist. Even traffic from existing user
# contacts will be blocked.
#
# Example config (make sure "firewall" is in modules_enabled):
#
#   firewall_scripts = { "module:scripts/jabberspam-simple-blocklist.pfw" }
#
# For a more advanced ruleset, consider using spam-blocking.pfw
# and spam-blocklists.pfw.

%LIST blocklist: https://cdn.jsdelivr.net/gh/jabberspam/blacklist/blacklist.txt

::deliver

CHECK LIST: blocklist contains $<@from|host>
BOUNCE=policy-violation (Your server is blocked due to spam)