Software /
code /
prosody-modules
Comparison
mod_firewall/README.markdown @ 4965:d7684aa81d8f
mod_firewall: README: Correct mention of 'JUMP_CHAIN' to 'JUMP CHAIN'
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 28 Jun 2022 16:28:44 +0100 |
parent | 4583:bb8459c220c9 |
child | 4966:4ffd6551f4bb |
comparison
equal
deleted
inserted
replaced
4964:b1c4e78e669e | 4965:d7684aa81d8f |
---|---|
646 preroute Applies to incoming stanzas from local users, before any routing rules are applied | 646 preroute Applies to incoming stanzas from local users, before any routing rules are applied |
647 | 647 |
648 A chain is begun by a line `::name` where 'name' is the name of the chain you want the following rules to be | 648 A chain is begun by a line `::name` where 'name' is the name of the chain you want the following rules to be |
649 inserted into. If no chain is specified, rules are put into the 'deliver' chain. | 649 inserted into. If no chain is specified, rules are put into the 'deliver' chain. |
650 | 650 |
651 It is possible to create custom chains (useful with the JUMP_CHAIN action described below). User-created | 651 It is possible to create custom chains (useful with the `JUMP CHAIN` action described below). User-created |
652 chains must begin with "user/", e.g. "user/spam_filtering". | 652 chains must begin with "user/", e.g. "user/spam_filtering". |
653 | 653 |
654 Example of chain use: | 654 Example of chain use: |
655 | 655 |
656 # example.com's firewall script | 656 # example.com's firewall script |